<?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: Using WordPress&#8217;s &#8220;Upgrade Automatically&#8221; Feature</title>
	<atom:link href="http://thecodetrain.co.uk/2009/12/using-wordpresss-upgrade-automatically-feature/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecodetrain.co.uk/2009/12/using-wordpresss-upgrade-automatically-feature/</link>
	<description>Where Neil Crosby talks about coding on the train...</description>
	<lastBuildDate>Sat, 21 Aug 2010 06:15:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Neil Crosby</title>
		<link>http://thecodetrain.co.uk/2009/12/using-wordpresss-upgrade-automatically-feature/comment-page-1/#comment-1031</link>
		<dc:creator>Neil Crosby</dc:creator>
		<pubDate>Wed, 23 Dec 2009 13:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://thecodetrain.co.uk/?p=339#comment-1031</guid>
		<description>&lt;p&gt;Hi Shahid.  Do you have the ability to &lt;code&gt;ssh&lt;/code&gt; into your servers? If you can, then this is where you&#039;ll perform the &lt;code&gt;chown&lt;/code&gt; commands.  If not, ask your server admins if they can enable FTPS access for you so that WordPress can update itself that way.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Shahid.  Do you have the ability to <code>ssh</code> into your servers? If you can, then this is where you&#8217;ll perform the <code>chown</code> commands.  If not, ask your server admins if they can enable FTPS access for you so that WordPress can update itself that way.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Shahid</title>
		<link>http://thecodetrain.co.uk/2009/12/using-wordpresss-upgrade-automatically-feature/comment-page-1/#comment-1029</link>
		<dc:creator>Shahid</dc:creator>
		<pubDate>Wed, 23 Dec 2009 09:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://thecodetrain.co.uk/?p=339#comment-1029</guid>
		<description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;I am using Wordpress 2.8 at my blog.
I tried upgrading automatically but it did not work. I dont know how to do the chown stuff. Isn&#039;t there any easy way ?&lt;/p&gt;

&lt;p&gt;I also have another blog and I would like to upgrade to WP2.9 there also. Any suggestions or help etc ?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi,</p>

<p>I am using Wordpress 2.8 at my blog.
I tried upgrading automatically but it did not work. I dont know how to do the chown stuff. Isn&#8217;t there any easy way ?</p>

<p>I also have another blog and I would like to upgrade to WP2.9 there also. Any suggestions or help etc ?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bradley Wright</title>
		<link>http://thecodetrain.co.uk/2009/12/using-wordpresss-upgrade-automatically-feature/comment-page-1/#comment-1023</link>
		<dc:creator>Bradley Wright</dc:creator>
		<pubDate>Sun, 20 Dec 2009 14:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://thecodetrain.co.uk/?p=339#comment-1023</guid>
		<description>&lt;p&gt;To be honest, I don&#039;t know how else you&#039;d manage an in-admin console upgrade without either:&lt;/p&gt;

&lt;p&gt;a) Having the file system writable by www-data; or
b) Eval&#039;ing the code out of a database (ala TextPattern templates);&lt;/p&gt;

&lt;p&gt;Given how bad eval is, I&#039;d go for the file system upgrade.&lt;/p&gt;

&lt;p&gt;Incidentally, fastest way to do the &quot;open up perms and switch&quot; dance is to make yourself part of the www-data group, but own the files yourself:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;sudo chown -R crosby:www-data /path/to/files/*
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;&lt;p&gt;Then just add write permissions for group:&lt;/p&gt;&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;sudo chmod -R g+w /path/to/files/*
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;upgrade, and then remove perms:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;sudo chmod -R g-w /path/to/files/*
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Stick those commands as an alias inside your .bashrc and you&#039;re away.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>To be honest, I don&#8217;t know how else you&#8217;d manage an in-admin console upgrade without either:</p>

<p>a) Having the file system writable by www-data; or
b) Eval&#8217;ing the code out of a database (ala TextPattern templates);</p>

<p>Given how bad eval is, I&#8217;d go for the file system upgrade.</p>

<p>Incidentally, fastest way to do the &#8220;open up perms and switch&#8221; dance is to make yourself part of the www-data group, but own the files yourself:</p>

<pre><code>sudo chown -R crosby:www-data /path/to/files/*
</code></pre>

<p></p><p>Then just add write permissions for group:</p>

<pre><code>sudo chmod -R g+w /path/to/files/*
</code></pre>

<p>upgrade, and then remove perms:</p>

<pre><code>sudo chmod -R g-w /path/to/files/*
</code></pre>

<p>Stick those commands as an alias inside your .bashrc and you&#8217;re away.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Crosby</title>
		<link>http://thecodetrain.co.uk/2009/12/using-wordpresss-upgrade-automatically-feature/comment-page-1/#comment-1021</link>
		<dc:creator>Neil Crosby</dc:creator>
		<pubDate>Sat, 19 Dec 2009 23:27:09 +0000</pubDate>
		<guid isPermaLink="false">http://thecodetrain.co.uk/?p=339#comment-1021</guid>
		<description>&lt;p&gt;I must admit, whilst I was writing this I fully expected &lt;a href=&quot;http://intranation.com&quot; rel=&quot;nofollow&quot;&gt;somebody&lt;/a&gt; to reply saying &quot;but leaving the filesystem server writable is horribly insecure too!&quot;. So yup, locking the permissions down again after doing the upgrade is definitely a sensible thing to do.&lt;/p&gt;

&lt;p&gt;As for the wp-content bit, that was a slip of my hands whilst typing - I&#039;ve updated it now. Yup, when I changed the permissions I did it for the entire WP tree.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I must admit, whilst I was writing this I fully expected <a href="http://intranation.com" rel="nofollow">somebody</a> to reply saying &#8220;but leaving the filesystem server writable is horribly insecure too!&#8221;. So yup, locking the permissions down again after doing the upgrade is definitely a sensible thing to do.</p>

<p>As for the wp-content bit, that was a slip of my hands whilst typing &#8211; I&#8217;ve updated it now. Yup, when I changed the permissions I did it for the entire WP tree.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Mear</title>
		<link>http://thecodetrain.co.uk/2009/12/using-wordpresss-upgrade-automatically-feature/comment-page-1/#comment-1020</link>
		<dc:creator>Chris Mear</dc:creator>
		<pubDate>Sat, 19 Dec 2009 23:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://thecodetrain.co.uk/?p=339#comment-1020</guid>
		<description>&lt;p&gt;If this is for the WordPress core upgrade, wouldn&#039;t the root WordPress directory need to be writeable as well, not just the wp-content subdirectory?&lt;/p&gt;

&lt;p&gt;I had this set up like this and upgrading nicely, but it always felt a bit insecure. I&#039;m no security expert, but something about leaving your plugin and theme directories (and possibly more) writeable by the web server process feels a bit unnecessarily dangerous. Or am I being over-paranoid?&lt;/p&gt;

&lt;p&gt;The built-in upgrade system is just &lt;em&gt;so&lt;/em&gt; &lt;em&gt;nice&lt;/em&gt;, though, so these days I have the permissions locked down, and then temporarily open them up, do the upgrade through the web interface, and then lock them down again. Sounds like a hassle, but I find it easier than futzing around with zip files and remembering which files I&#039;m supposed to update manually.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>If this is for the WordPress core upgrade, wouldn&#8217;t the root WordPress directory need to be writeable as well, not just the wp-content subdirectory?</p>

<p>I had this set up like this and upgrading nicely, but it always felt a bit insecure. I&#8217;m no security expert, but something about leaving your plugin and theme directories (and possibly more) writeable by the web server process feels a bit unnecessarily dangerous. Or am I being over-paranoid?</p>

<p>The built-in upgrade system is just <em>so</em> <em>nice</em>, though, so these days I have the permissions locked down, and then temporarily open them up, do the upgrade through the web interface, and then lock them down again. Sounds like a hassle, but I find it easier than futzing around with zip files and remembering which files I&#8217;m supposed to update manually.</p>]]></content:encoded>
	</item>
</channel>
</rss>
