<?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>Jim&#039;s New World &#187; WPAU</title> <atom:link href="http://www.theczechs.net/blog/tag/wpau/feed/" rel="self" type="application/rss+xml" /><link>http://www.theczechs.net/blog</link> <description>Just another place to ramble on about nothing...</description> <lastBuildDate>Tue, 08 Nov 2011 20:26:22 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=</generator> <xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" /> <item><title>Searching for answers to WordPress upgrade issues</title><link>http://www.theczechs.net/blog/wordpress/answers-wordpress-upgrade-issues/</link> <comments>http://www.theczechs.net/blog/wordpress/answers-wordpress-upgrade-issues/#comments</comments> <pubDate>Sat, 11 Jul 2009 19:31:17 +0000</pubDate> <dc:creator>Jim</dc:creator> <category><![CDATA[Review]]></category> <category><![CDATA[WordPress]]></category> <category><![CDATA[automatic]]></category> <category><![CDATA[Fred Palma]]></category> <category><![CDATA[Leopard]]></category> <category><![CDATA[Mac]]></category> <category><![CDATA[OS X]]></category> <category><![CDATA[plugins]]></category> <category><![CDATA[server]]></category> <category><![CDATA[Techie Buzz]]></category> <category><![CDATA[upgrade]]></category> <category><![CDATA[WPAU]]></category> <guid
isPermaLink="false">http://www.theczechs.net/blog/?p=366</guid> <description><![CDATA[After never being able to upgrade WordPress in any sort of automatic, or painless, way, I've finally stumbled upon a configuration that seems to work.  In the end, it's all a matter of ownership and permissions, at least in my case.]]></description> <content:encoded><![CDATA[<p>I&#8217;ve had trouble upgrading (automatically or otherwise) my WordPress installation running on my OS X Server.  I&#8217;ve tried several &#8220;automatic&#8221; plugins, as well as the built-in WordPress tool.</p><p>I almost had success with the <a
title="WPAU plugin" href="http://techie-buzz.com/wordpress-plugins/wordpress-automatic-upgrade-plugin.html" target="_blank">WordPress Automatic Upgrade plugin</a> (WPAU).  Everything seemed to work, right up to the point of putting the site in maintenance mode.  But try as I might, even with a manual &#8220;.maintenance&#8221; file it would always fail.  Searched high and low, and came across several folks having similar (and different) upgrade woes.  Some posts indicated the WPAU plugin was &#8216;outdated&#8217; and no longer necessary since WordPress offers the functionality built-in.  But, previously that hadn&#8217;t worked for me.</p><p>I tried most of the solutions, which had varying levels of success for the folks posting to forums and blogs.  Finally came across one solution, which looked so simple, I couldn&#8217;t hurt by trying.  Check out <a
title="Fred Palma | Computer Scientist" href="http://fredpalma.com/automatic-wordpress-upgrade-error-error-there-was-an-error-connecting-to-the-server-please-verify-the-settings-are-correct/comment-page-1/#comment-391" target="_blank">Fred Palma&#8217;s easy solution</a>. It simply entails changing the owner and group to be &#8216;owned&#8217; by the web server itself.  On my server, I made one small change, that being that the owner and group are &#8220;www&#8221; instead of Fred&#8217;s &#8220;www-data&#8221; since I was familiar with that owner/group on installation.</p><p>Next, I had to figure out the correct settings for the WordPress routine.  There were only a few things to configure, but try as I might, using the server name (or variations) would always fail.  Searching for those failure messages landed me on a support forum post that indicated the individual had entered &#8220;localhost&#8221; as the server name.  Something obscure indicated the server couldn&#8217;t connect to itself and this might be a possible solution.  Sure enough, it worked, with the proper username/password credentials.</p><p>The update to 2.8.1 was painless, once everything was configured properly.  Now I have to go back and clean up file permissions and other messes I made. I&#8217;ll delete the WPAU plugin and perform a general review to make sure we&#8217;re all up and running properly, as well.</p> ]]></content:encoded> <wfw:commentRss>http://www.theczechs.net/blog/wordpress/answers-wordpress-upgrade-issues/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
