<?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>ScreencastWorldHow To Fix &#187; ScreencastWorld</title>
	<atom:link href="http://screencastworld.com/category/magento/how-to-fix/feed" rel="self" type="application/rss+xml" />
	<link>http://screencastworld.com</link>
	<description>How To, Tips, Tricks, Screencasts, and Video Tutorials</description>
	<lastBuildDate>Wed, 13 Apr 2011 22:49:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>How To Fix: Warning: date(): It is not safe to rely on the system&#8217;s timezone setting</title>
		<link>http://screencastworld.com/2010/08/magento/how-to-fix/how-to-fix-warning-date-it-is-not-safe-to-rely-on-the-systems-timezone-setting</link>
		<comments>http://screencastworld.com/2010/08/magento/how-to-fix/how-to-fix-warning-date-it-is-not-safe-to-rely-on-the-systems-timezone-setting#comments</comments>
		<pubDate>Wed, 25 Aug 2010 19:09:24 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=633</guid>
		<description><![CDATA[If you try to upgrade Magento using the command line PEAR interface you may encounter the following: ./pear mage-setup Running initial setup... Warning: date(): It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those [...]]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/08/magento/how-to-fix/how-to-fix-warning-date-it-is-not-safe-to-rely-on-the-systems-timezone-setting/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Fix: Failed opening required &#8216;../magento/downloader/pearlib/php/PEAR.php&#8217;</title>
		<link>http://screencastworld.com/2010/08/magento/how-to-fix/how-to-fix-failed-opening-required-magentodownloaderpearlibphppear-php</link>
		<comments>http://screencastworld.com/2010/08/magento/how-to-fix/how-to-fix-failed-opening-required-magentodownloaderpearlibphppear-php#comments</comments>
		<pubDate>Thu, 19 Aug 2010 17:56:42 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=622</guid>
		<description><![CDATA[I recently came across the situation where I was no longer unable to access the Magento Connect area of a previously working installation of Magento.  After logging in to the backend and going to System -&#62; Magento Connect -&#62; Magento Connect Manager I got the following error (note: I had &#8220;ini_set(&#8216;display_errors&#8217;, 1);&#8221; uncommented in my [...]]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/08/magento/how-to-fix/how-to-fix-failed-opening-required-magentodownloaderpearlibphppear-php/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento: Resolving &#8220;Invalid mode for clean() method&#8221;</title>
		<link>http://screencastworld.com/2010/07/magento/how-to-fix/magento-resolving-invalid-mode-for-clean-method</link>
		<comments>http://screencastworld.com/2010/07/magento/how-to-fix/magento-resolving-invalid-mode-for-clean-method#comments</comments>
		<pubDate>Wed, 21 Jul 2010 19:11:56 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[installation]]></category>
		<category><![CDATA[magento commerce]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=619</guid>
		<description><![CDATA[This post provides the solution to the "Invalid mode for clean() method" error message after upgrading Magento 1.3.2.4 to 1.4.1.0.]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/07/magento/how-to-fix/magento-resolving-invalid-mode-for-clean-method/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP Fatal error:  Call to a member function toHtml() on a non-object in &#8230;/Layout.php on line 529</title>
		<link>http://screencastworld.com/2010/07/magento/how-to-fix/php-fatal-error-call-to-a-member-function-tohtml-on-a-non-object-in-layout-php-on-line-529</link>
		<comments>http://screencastworld.com/2010/07/magento/how-to-fix/php-fatal-error-call-to-a-member-function-tohtml-on-a-non-object-in-layout-php-on-line-529#comments</comments>
		<pubDate>Sun, 18 Jul 2010 18:29:50 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>
		<category><![CDATA[template]]></category>
		<category><![CDATA[theme]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=615</guid>
		<description><![CDATA[This post shows how to debug and fix "PHP Fatal error:  Call to a member function toHtml() on a non-object in /www/www.yourdomain.com/magento/app/code/core/Mage/Core/Model/Layout.php on line 529" which is often seen after upgrading Magento Commerce.]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/07/magento/how-to-fix/php-fatal-error-call-to-a-member-function-tohtml-on-a-non-object-in-layout-php-on-line-529/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Magento: How To Fix &#8220;Unable detect system directory: report&#8221;</title>
		<link>http://screencastworld.com/2010/07/magento/how-to-fix/magento-how-to-fix-unable-detect-system-directory-report</link>
		<comments>http://screencastworld.com/2010/07/magento/how-to-fix/magento-how-to-fix-unable-detect-system-directory-report#comments</comments>
		<pubDate>Tue, 13 Jul 2010 17:49:45 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=612</guid>
		<description><![CDATA[This post shows how to debug and fix the "Unable detect system directory: report" error message.]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/07/magento/how-to-fix/magento-how-to-fix-unable-detect-system-directory-report/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento: How To Fix &#8220;SQLSTATE[42000]: Syntax error or access violation&#8221;</title>
		<link>http://screencastworld.com/2010/07/magento/how-to-fix/magento-how-to-fix-sqlstate42000-syntax-error-or-access-violation</link>
		<comments>http://screencastworld.com/2010/07/magento/how-to-fix/magento-how-to-fix-sqlstate42000-syntax-error-or-access-violation#comments</comments>
		<pubDate>Fri, 09 Jul 2010 18:53:33 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[1.3]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[installation]]></category>
		<category><![CDATA[magento commerce]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=608</guid>
		<description><![CDATA[This post shows how to fix the message "SQLSTATE[42000]: Syntax error or access violation: 1044 Access denied for user 'dbusername'@'localhost' to database 'dbname'" which was seen during a Magento Commerce install/upgrade procedure.]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/07/magento/how-to-fix/magento-how-to-fix-sqlstate42000-syntax-error-or-access-violation/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Enable Google Analytics for your Magento Site</title>
		<link>http://screencastworld.com/2010/04/magento/v1-4/how-to-enable-google-analytics-for-your-magento-site</link>
		<comments>http://screencastworld.com/2010/04/magento/v1-4/how-to-enable-google-analytics-for-your-magento-site#comments</comments>
		<pubDate>Fri, 30 Apr 2010 18:45:09 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[Magento 1.4.x]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[eCommerce]]></category>
		<category><![CDATA[Google Analytics]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>
		<category><![CDATA[tip]]></category>
		<category><![CDATA[trick]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=510</guid>
		<description><![CDATA[This 'How To' article shows you how to find your Google Analytics web property ID/UA Number and how to enable Google Analytics within Magento Commerce.]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/04/magento/v1-4/how-to-enable-google-analytics-for-your-magento-site/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento Commerce: Fixing &#8220;Exception printing is disabled by default for security reasons&#8221;</title>
		<link>http://screencastworld.com/2010/04/articles/magento-commerce-exception-printing-is-disabled-by-default-for-security-reasons</link>
		<comments>http://screencastworld.com/2010/04/articles/magento-commerce-exception-printing-is-disabled-by-default-for-security-reasons#comments</comments>
		<pubDate>Thu, 08 Apr 2010 19:40:02 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[Magento 1.4.x]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=458</guid>
		<description><![CDATA[Understanding and enabling error reporting in Magento Commerce to handle events such as these:

There has been an error processing your request
Exception printing is disabled by default for security reasons
Error log record number: XXXXXXXXXXXXXXX]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/04/articles/magento-commerce-exception-printing-is-disabled-by-default-for-security-reasons/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Magento Commerce Index Manager: How To Fix &#8220;Could not determine temp directory, please specify a cache_dir manually&#8221;</title>
		<link>http://screencastworld.com/2010/04/articles/magento-commerce-index-manager-how-to-fix-could-not-determine-temp-directory-please-specify-a-cache_dir-manually</link>
		<comments>http://screencastworld.com/2010/04/articles/magento-commerce-index-manager-how-to-fix-could-not-determine-temp-directory-please-specify-a-cache_dir-manually#comments</comments>
		<pubDate>Tue, 06 Apr 2010 17:34:25 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[Magento 1.4.x]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=451</guid>
		<description><![CDATA[One of the new features in Magento Commerce CE 1.4 is "Index Management".  On some hosting platforms building the indexes can fail with "Could not determine temp directory, please specify a cache_dir manually".  This article shows you hot to fix this.]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/04/articles/magento-commerce-index-manager-how-to-fix-could-not-determine-temp-directory-please-specify-a-cache_dir-manually/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento Commerce 1.4: How To Fix &#8216;Unable to submit your request. Please, try again later’ on the Contact Us form</title>
		<link>http://screencastworld.com/2010/03/articles/magento-commerce-1-4-how-to-fix-unable-to-submit-your-request-please-try-again-later%e2%80%99-on-the-contact-us-form</link>
		<comments>http://screencastworld.com/2010/03/articles/magento-commerce-1-4-how-to-fix-unable-to-submit-your-request-please-try-again-later%e2%80%99-on-the-contact-us-form#comments</comments>
		<pubDate>Wed, 10 Mar 2010 14:29:22 +0000</pubDate>
		<dc:creator>ScreencastWorld</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[How To Fix]]></category>
		<category><![CDATA[Magento 1.4.x]]></category>
		<category><![CDATA[1.3]]></category>
		<category><![CDATA[1.4]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[magento commerce]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://screencastworld.com/?p=440</guid>
		<description><![CDATA[If your Contact Us page is broken and now returns "Unable to submit your request.  Please try again later", this article will show you how to fix it.]]></description>
		<wfw:commentRss>http://screencastworld.com/2010/03/articles/magento-commerce-1-4-how-to-fix-unable-to-submit-your-request-please-try-again-later%e2%80%99-on-the-contact-us-form/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

