<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Tutorial: Using the WP_Filesystem</title>
	<atom:link href="http://ottopress.com/2011/tutorial-using-the-wp_filesystem/feed/" rel="self" type="application/rss+xml" />
	<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/</link>
	<description>You have to use an Ottopress to get fresh squeezed Otto.</description>
	<lastBuildDate>Fri, 17 May 2013 22:57:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta3-24284</generator>
	<item>
		<title>By: Automatisches WordPress-Upgrade bei lokalen Installationen nutzen &#124; Frontend Log</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11753</link>
		<dc:creator>Automatisches WordPress-Upgrade bei lokalen Installationen nutzen &#124; Frontend Log</dc:creator>
		<pubDate>Mon, 08 Apr 2013 13:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11753</guid>
		<description><![CDATA[[...] Editing wp-config.php: WordPress Upgrade Constants Tutorial: Using the WP_Filesystem [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Editing wp-config.php: WordPress Upgrade Constants Tutorial: Using the WP_Filesystem [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to do damn near anything with WordPress &#124; Stephanie Leary</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11742</link>
		<dc:creator>How to do damn near anything with WordPress &#124; Stephanie Leary</dc:creator>
		<pubDate>Tue, 02 Apr 2013 03:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11742</guid>
		<description><![CDATA[[...] APIs: filesystem, HTTP, rewrite, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] APIs: filesystem, HTTP, rewrite, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11719</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Thu, 21 Mar 2013 13:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11719</guid>
		<description><![CDATA[The $type value, in this case, can be anything and you&#039;d get much the same result. The only values actually being checked for at this level are &#039;direct&#039; or &#039;ftpext&#039; (for ssl FTP connections, the ftpext method is required). All the other methods require special setup in the wp-config.php file. So specifying &#039;ftp&#039; here is just for convenience, so it won&#039;t use &#039;direct&#039;.]]></description>
		<content:encoded><![CDATA[<p>The $type value, in this case, can be anything and you&#8217;d get much the same result. The only values actually being checked for at this level are &#8216;direct&#8217; or &#8216;ftpext&#8217; (for ssl FTP connections, the ftpext method is required). All the other methods require special setup in the wp-config.php file. So specifying &#8216;ftp&#8217; here is just for convenience, so it won&#8217;t use &#8216;direct&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul_wp</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11716</link>
		<dc:creator>paul_wp</dc:creator>
		<pubDate>Thu, 21 Mar 2013 00:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11716</guid>
		<description><![CDATA[Otto,
in your example you&#039;re forcing an ftp method. I couldn&#039;t find that one in the code. 
It seems the valid methods are &#039;ftpext&#039;, &#039;ftpsockets&#039; and &#039;ssh2&#039;]]></description>
		<content:encoded><![CDATA[<p>Otto,<br />
in your example you&#8217;re forcing an ftp method. I couldn&#8217;t find that one in the code.<br />
It seems the valid methods are &#8216;ftpext&#8217;, &#8216;ftpsockets&#8217; and &#8216;ssh2&#8242;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress: Necessary Reading &#124; Tom J Nowell</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11605</link>
		<dc:creator>WordPress: Necessary Reading &#124; Tom J Nowell</dc:creator>
		<pubDate>Tue, 05 Feb 2013 15:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11605</guid>
		<description><![CDATA[[...] Using the WordPress File System API [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Using the WordPress File System API [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Knight</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11591</link>
		<dc:creator>Peter Knight</dc:creator>
		<pubDate>Fri, 01 Feb 2013 23:25:03 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11591</guid>
		<description><![CDATA[Hi Otto, what would be the most secure way to deal with a caching solution? I noticed Total Cache for example writes files directly (no wp file api), I think another caching plugin stores the user credentials (if required) in the database and another article mentions storing credentials in wp-config.php as constants. I&#039;m not sure the latter are that much more secure because if a the credentials are compromised a hacker would have free range.]]></description>
		<content:encoded><![CDATA[<p>Hi Otto, what would be the most secure way to deal with a caching solution? I noticed Total Cache for example writes files directly (no wp file api), I think another caching plugin stores the user credentials (if required) in the database and another article mentions storing credentials in wp-config.php as constants. I&#8217;m not sure the latter are that much more secure because if a the credentials are compromised a hacker would have free range.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kenth Hagström</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11523</link>
		<dc:creator>Kenth Hagström</dc:creator>
		<pubDate>Wed, 02 Jan 2013 14:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11523</guid>
		<description><![CDATA[Is it possible to upload files outside the WordPress root directory by using the WP_Filesystem?]]></description>
		<content:encoded><![CDATA[<p>Is it possible to upload files outside the WordPress root directory by using the WP_Filesystem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11503</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Sun, 23 Dec 2012 04:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11503</guid>
		<description><![CDATA[Look at where I call request_filesystem_credentials. If the result of that call is anything other than false, then you either don&#039;t need credentials, or already have the necessary credentials. In which case, you continue on as per usual.

However, if that does return false, or if the WP_Filesystem($creds) call fails, then you don&#039;t have the proper credentials yet, and you must therefore get them from the user somehow, in which case you have to show them some kind of form.]]></description>
		<content:encoded><![CDATA[<p>Look at where I call request_filesystem_credentials. If the result of that call is anything other than false, then you either don&#8217;t need credentials, or already have the necessary credentials. In which case, you continue on as per usual.</p>
<p>However, if that does return false, or if the WP_Filesystem($creds) call fails, then you don&#8217;t have the proper credentials yet, and you must therefore get them from the user somehow, in which case you have to show them some kind of form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe Shackle</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11502</link>
		<dc:creator>Gabe Shackle</dc:creator>
		<pubDate>Sun, 23 Dec 2012 03:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11502</guid>
		<description><![CDATA[Do you have any examples of how to write a file using the WP_Filesystem API that does not require a form submission?]]></description>
		<content:encoded><![CDATA[<p>Do you have any examples of how to write a file using the WP_Filesystem API that does not require a form submission?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottopress.com/2011/tutorial-using-the-wp_filesystem/comment-page-1/#comment-11399</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Thu, 15 Nov 2012 23:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://ottopress.com/?p=471#comment-11399</guid>
		<description><![CDATA[If you&#039;re getting an error from the put_contents() call, then you may want to store the error in a variable (it&#039;ll probably be a WP_Error object) and var_dump it to see what sort of error it is that you&#039;re getting.]]></description>
		<content:encoded><![CDATA[<p>If you&#8217;re getting an error from the put_contents() call, then you may want to store the error in a variable (it&#8217;ll probably be a WP_Error object) and var_dump it to see what sort of error it is that you&#8217;re getting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Object Caching 421/437 objects using xcache

 Served from: ottodestruct.com @ 2013-05-18 21:01:13 by W3 Total Cache -->