<?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>farscan blogs &#187; error</title>
	<atom:link href="http://www.farscan.com/blogs/tag/error/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.farscan.com/blogs</link>
	<description>technology, innovation &#38; real-world expertise</description>
	<lastBuildDate>Wed, 09 Feb 2011 18:41:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Resolving WordPress memory exhaustion</title>
		<link>http://www.farscan.com/blogs/2009/03/wordpress-woes-contd/</link>
		<comments>http://www.farscan.com/blogs/2009/03/wordpress-woes-contd/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 17:45:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[setup]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.farscan.com/blogs/?p=263</guid>
		<description><![CDATA[This article explains steps to resolve memory allocation related errors from Wordpress.]]></description>
			<content:encoded><![CDATA[<p>Here are some tips for curing the memory allocation errors WP Users may see from various modules when they try to edit, preview or publish a post.</p>
<p>&#8220;Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 500001 bytes)&#8230;..&#8221;</p>
<p>PHP memory allocation can be increased several ways.</p>
<p>1. Server wide PHP memory size can be increased via php.ini or similar and requires your hosting service partner&#8217;s help.<br />
2. Easier solutions are either to</p>
<p style="padding-left: 30px;">a. add the line <code>php_value memory_limit 32M</code> to your .htaccess file, or</p>
<p style="padding-left: 30px;">b. add the line <code>define('WP_MEMORY_LIMIT', '32M'); </code>to your wp-config.php file in your WordPress installation folder.</p>
<p style="padding-left: 30px;">Note: .htaccess is usually hidden if it exists (in your root Web folder). You may need to turn on the reveal hidden files option in your FTP client to see it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.farscan.com/blogs/2009/03/wordpress-woes-contd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Upload Issue resolution</title>
		<link>http://www.farscan.com/blogs/2009/03/wordpress-installation-woes/</link>
		<comments>http://www.farscan.com/blogs/2009/03/wordpress-installation-woes/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 05:38:45 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[setup]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.farscan.com/blogs/?p=31</guid>
		<description><![CDATA[Finally, wordpress is installed and almost all plug-ins are up. Trying to post an image threw up a cryptic error message “The uploaded file could not be moved to&#8230;” Looks like the default installation path for &#8220;Store uploads in this folder&#8221; is set as &#8220;"wp-content". Here&#8217;s what is need to fix this: Change the value [...]]]></description>
			<content:encoded><![CDATA[<p>Finally, wordpress is installed and almost all plug-ins are up. Trying to post an image threw up a cryptic error message</p>
<h3>“The uploaded file could not be moved to&#8230;”</h3>
<p>Looks like the default installation path for &#8220;<strong>Store uploads in this folder</strong>&#8221; is set as &#8220;<span class="setting-description"><code>"wp-content"</code></span>. Here&#8217;s what is need to fix this:</p>
<ul>
<li>Change the value from  &#8220;<span class="setting-description"><code>"wp-content" </code></span>to &#8220;<span class="setting-description"><code>wp-content/upLoads"</code></span></li>
<li>Create a directory called <span class="setting-description"><code>"upLoads"</code></span> under the directory &#8220;<span class="setting-description"><code>wp-content". </code></span>Note that the folder names are case sensitive.</li>
<li>Assign World  &#8216;Read/Write/Execute&#8217; permission (i.e: 0&#215;777) for the new directory. 0&#215;666 (Just Read/Write) doesn&#8217;t seem to cut it.</li>
</ul>
<p>That should do it.</p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.farscan.com%2Fblogs%2F2009%2F03%2Fwordpress-installation-woes%2F&amp;title=WordPress%20Upload%20Issue%20resolution"><img src="http://www.farscan.com/blogs/wp-content/plugins/add-to-any/share_save_120_16.png" width="120" height="16" alt="Share"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://www.farscan.com/blogs/2009/03/wordpress-installation-woes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

