 
    
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>errors Archives - Complete, Concrete, Concise</title>
	<atom:link href="https://complete-concrete-concise.com/tag/errors/feed/" rel="self" type="application/rss+xml" />
	<link>https://complete-concrete-concise.com/tag/errors/</link>
	<description>Practical Information Without The Bloat</description>
	<lastBuildDate>Thu, 19 Jan 2012 12:27:42 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>XAMPP &#8211; Fixing &#039;Strict Standards&#039; Errors</title>
		<link>https://complete-concrete-concise.com/web-tools/xampp-fixing-strict-standards-errors/</link>
					<comments>https://complete-concrete-concise.com/web-tools/xampp-fixing-strict-standards-errors/#comments</comments>
		
		<dc:creator><![CDATA[richardsplanet]]></dc:creator>
		<pubDate>Thu, 19 Jan 2012 12:27:42 +0000</pubDate>
				<category><![CDATA[Web Tools]]></category>
		<category><![CDATA[1.7.4]]></category>
		<category><![CDATA[1.7.7]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[joomla]]></category>
		<category><![CDATA[strict standards]]></category>
		<category><![CDATA[XAMPP]]></category>
		<guid isPermaLink="false">http://complete-concrete-concise.com/?p=1367</guid>

					<description><![CDATA[<p>This tutorial is for XAMPP 1.7.4 and XAMPP 1.7.7. It addresses the problem of many errors being generated by popular PHP applications (notably Joomla!) that you would expect to work, but, instead, generate lots of errors. If you have installed XAMPP 1.7.4 or XAMPP 1.7.7, you may have noticed that some applications (notably Joomla 1.5.x, [&#8230;]</p>
<p>The post <a href="https://complete-concrete-concise.com/web-tools/xampp-fixing-strict-standards-errors/">XAMPP &#8211; Fixing &#039;Strict Standards&#039; Errors</a> appeared first on <a href="https://complete-concrete-concise.com">Complete, Concrete, Concise</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="c1">
<p>This tutorial is for XAMPP 1.7.4 and XAMPP 1.7.7.</p>
<p>It addresses the problem of many errors being generated by popular PHP applications (notably Joomla!) that you would expect to work, but, instead, generate lots of errors.</p>
</div>
<p>If you have installed XAMPP 1.7.4 or XAMPP 1.7.7, you may have noticed that some applications (notably Joomla 1.5.x, 1.6.x, and 1.7.x) generate lots of errors along the lines of:</p>
<p><code><strong>Strict Standards:</strong> Accessing static property JCache::$_handler as non static in <strong>C:\xampp\htdocs\joomla\libraries\joomla\cache\cache.php</strong> on line 420</code></p>
<p>This happens because these versions of XAMPP ship with default PHP settings that cause the PHP interpreter to choke on poor programming practices and deprecated (obsolete) language features. For developers, this is a good thing, but for the general user, it causes a lot of grief.</p>
<p><strong>(1) Go</strong> to the php directory under XAMPP. Normally, this would be <strong>C:\XAMPP\php</strong>, but you may have installed it to a different drive or directory (mine is installed in C:\xampp-1.7.4). <strong>Locate</strong> the file named<em><u> php.ini</u></em> . <strong>Open </strong>this file using a plain text editor &#8211; like notepad. Using a word processor (like Word) will very likely seriously corrupt the file. (I use an application called <a href="http://notepad-plus-plus.org/">Notepad++</a>). <strong>Note:</strong> The icon associated with <strong><em>php.ini</em> </strong>will depend on what application is associated with <strong><em>.ini</em></strong> files.</p>
<p><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/01/xampp-fixing-strict-standards-errors.png" alt="" border="0" class="centered" /></p>
<div class="c1">
<p>The file is 86KB in XAMPP 1.7.4 and 1.7.7.</p>
<p>There are two files called <u><em>php.ini-development</em></u> and <u><em>php.ini-production</em></u>, you might think you could just rename the php.ini file and use the production one, but it doesn&#8217;t work either.</p>
</div>
<p><strong>(2) Find</strong> the line <span class="i1">error_reporting = E_ALL | E_STRICT</span> . In the XAMPP 1.7.4 and 1.7.7, this is line 516:</p>
<p><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/01/xampp-fixing-strict-standards-errors-2.png" alt="" border="0" class="centered" /></p>
<p><strong>(3) Change</strong> the <em>E_ALL | E_STRICT</em> to <strong>E_ALL &#038; ~E_NOTICE &#038; ~E_DEPRECATED</strong>.</p>
<p><strong>(4) Save</strong> the file.</p>
<p><strong>(5) Restart</strong> the Apache server. The easiest way is to open the XAMPP control panel and <strong>click </strong>on the <u>Stop</u> button. Then <strong>click </strong>on <u>Start</u> to restart it. (You could also reboot the computer, but that is not necessary.)</p>
<p><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/01/xampp-fixing-strict-standards-errors-3.png" alt="" border="0" class="centered" /><br />
</p>
<p>The post <a href="https://complete-concrete-concise.com/web-tools/xampp-fixing-strict-standards-errors/">XAMPP &#8211; Fixing &#039;Strict Standards&#039; Errors</a> appeared first on <a href="https://complete-concrete-concise.com">Complete, Concrete, Concise</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://complete-concrete-concise.com/web-tools/xampp-fixing-strict-standards-errors/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
			</item>
	</channel>
</rss>
