<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: WordPress: Could not create directory &#8211; Plugin Install Failed</title>
	<atom:link href="http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/feed/" rel="self" type="application/rss+xml" />
	<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/</link>
	<description>Geekism. Graphic Design. Web-Development.</description>
	<lastBuildDate>Tue, 03 Jan 2012 16:07:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Rômulo</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-957</link>
		<dc:creator>Rômulo</dc:creator>
		<pubDate>Tue, 03 Jan 2012 16:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-957</guid>
		<description>I fix this issue by configuring the local ftp server write permitions</description>
		<content:encoded><![CDATA[<p>I fix this issue by configuring the local ftp server write permitions</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nano</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-924</link>
		<dc:creator>Nano</dc:creator>
		<pubDate>Tue, 16 Aug 2011 17:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-924</guid>
		<description>I had this problem but it was all due to wordpress being installed on a local machine.  In this case a Mac running Mamp. The fix was to run this command in terminal to chown -R _www:staff wordpress

replacing wordpress with the location of wordpress installation</description>
		<content:encoded><![CDATA[<p>I had this problem but it was all due to wordpress being installed on a local machine.  In this case a Mac running Mamp. The fix was to run this command in terminal to chown -R _www:staff wordpress</p>
<p>replacing wordpress with the location of wordpress installation</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: name32</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-921</link>
		<dc:creator>name32</dc:creator>
		<pubDate>Fri, 05 Aug 2011 19:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-921</guid>
		<description>Perhaps it works, open your PHPmyAdmin,
Search in database: &quot;path&quot;
Browse .. match(es) inside table wp_options
Edit value : upload_url_path</description>
		<content:encoded><![CDATA[<p>Perhaps it works, open your PHPmyAdmin,<br />
Search in database: &#8220;path&#8221;<br />
Browse .. match(es) inside table wp_options<br />
Edit value : upload_url_path</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lupee</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-561</link>
		<dc:creator>lupee</dc:creator>
		<pubDate>Wed, 11 May 2011 18:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-561</guid>
		<description>Could not create directory. /home/luthfi/public_html/staractoractress.com/wp-content/upgrade/google-analytics-for-wordpress.tmp/google-analytics-for-wordpress


how do I fix??</description>
		<content:encoded><![CDATA[<p>Could not create directory. /home/luthfi/public_html/staractoractress.com/wp-content/upgrade/google-analytics-for-wordpress.tmp/google-analytics-for-wordpress</p>
<p>how do I fix??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alistair</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-553</link>
		<dc:creator>Alistair</dc:creator>
		<pubDate>Tue, 12 Apr 2011 02:55:53 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-553</guid>
		<description>Excellent, Joe! Deactivating AskApache worked for me.</description>
		<content:encoded><![CDATA[<p>Excellent, Joe! Deactivating AskApache worked for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-550</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Sun, 10 Apr 2011 12:45:03 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-550</guid>
		<description>I had similar problems. After scratching my head and trying so many solutions. I remembered I had installed askapache plugin which password protects certain directories. 

Soultion: Deactivate it &gt; upgrade &gt; Reactivate.

It worked for me...</description>
		<content:encoded><![CDATA[<p>I had similar problems. After scratching my head and trying so many solutions. I remembered I had installed askapache plugin which password protects certain directories. </p>
<p>Soultion: Deactivate it &gt; upgrade &gt; Reactivate.</p>
<p>It worked for me&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeM</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-532</link>
		<dc:creator>MikeM</dc:creator>
		<pubDate>Fri, 04 Mar 2011 21:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-532</guid>
		<description>I was getting this error when trying to do a full Wordpress upgrade (via the dashboard).

None of the above worked for me in making that error message go away, but I discovered it worked great once I manually deleted the wp-content/upgrade directory.

Previously my ftp user had had full rwx access to this directory. I&#039;m guessing it was left behind (with nothing in it) by a previous upgrade, and for whatever reason the mkdir logic wasn&#039;t smart enough to notice the directory already existed. That&#039;s just my guess, however.</description>
		<content:encoded><![CDATA[<p>I was getting this error when trying to do a full WordPress upgrade (via the dashboard).</p>
<p>None of the above worked for me in making that error message go away, but I discovered it worked great once I manually deleted the wp-content/upgrade directory.</p>
<p>Previously my ftp user had had full rwx access to this directory. I&#8217;m guessing it was left behind (with nothing in it) by a previous upgrade, and for whatever reason the mkdir logic wasn&#8217;t smart enough to notice the directory already existed. That&#8217;s just my guess, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sasha</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-527</link>
		<dc:creator>sasha</dc:creator>
		<pubDate>Tue, 01 Mar 2011 10:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-527</guid>
		<description>I looked at this file and the lines you mention are already included.
Still I get this error and it started to occur after I installed a wordpress multisite in the root. The admin panel etc.. is up but I cant install any theme or plugin.
 
Before that I the latest version at its own db working just fine.
Now both of them give the error. I tried it on other domains and getting the same.</description>
		<content:encoded><![CDATA[<p>I looked at this file and the lines you mention are already included.<br />
Still I get this error and it started to occur after I installed a wordpress multisite in the root. The admin panel etc.. is up but I cant install any theme or plugin.</p>
<p>Before that I the latest version at its own db working just fine.<br />
Now both of them give the error. I tried it on other domains and getting the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leah</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-467</link>
		<dc:creator>Leah</dc:creator>
		<pubDate>Mon, 27 Sep 2010 11:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-467</guid>
		<description>I was having some issues with a host where the only way I could upload images from within WP was to have the uploads folder CHMOD to 777 which is not safe. Even more annoying, plugins were going to the uploads folder no matter how I set paths. I found an awesome plugin, WP Easy Uploader. Once this is installed, you can keep your folders locked down,not have to monkey with permissions or paths, and best of all, no longer have upload failures. I hope this helps someone.
http://wordpress.org/extend/plugins/wp-easy-uploader/</description>
		<content:encoded><![CDATA[<p>I was having some issues with a host where the only way I could upload images from within WP was to have the uploads folder CHMOD to 777 which is not safe. Even more annoying, plugins were going to the uploads folder no matter how I set paths. I found an awesome plugin, WP Easy Uploader. Once this is installed, you can keep your folders locked down,not have to monkey with permissions or paths, and best of all, no longer have upload failures. I hope this helps someone.<br />
<a href="http://wordpress.org/extend/plugins/wp-easy-uploader/" rel="nofollow">http://wordpress.org/extend/plugins/wp-easy-uploader/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allen</title>
		<link>http://stuff24.de/blog/wordpress-could-not-create-directory-plugin-install-failed/comment-page-1/#comment-358</link>
		<dc:creator>allen</dc:creator>
		<pubDate>Tue, 10 Aug 2010 15:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://stuff24.de/blog/?p=50#comment-358</guid>
		<description>Hey oposiciones, that&#039;s what got me going after horsing around with this problem for a while. I wonder if there&#039;s some log or other facility that would provide some information to speed-up the process of deciphering the fact that it&#039;s a permissions or ownership issue?</description>
		<content:encoded><![CDATA[<p>Hey oposiciones, that&#8217;s what got me going after horsing around with this problem for a while. I wonder if there&#8217;s some log or other facility that would provide some information to speed-up the process of deciphering the fact that it&#8217;s a permissions or ownership issue?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

