<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: Is there a Wordpress expert in the house?</title>
	<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house/</link>
	<description>Comments on Ask MetaFilter post Is there a Wordpress expert in the house?</description>
	<pubDate>Mon, 06 Oct 2008 18:11:47 -0800</pubDate>
	<lastBuildDate>Mon, 06 Oct 2008 18:11:47 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: Is there a Wordpress expert in the house?</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house</link>	
		<description>I&apos;ve got a really odd problem after a failed upgrade last night. I was upgrading a site to the newest version with the Wordpress Auto Upgrade plugin. I have used that plugin in the past with the site without issue. Last night it completed the preliminary checks and reported all was ok, and then when I clicked to begin upgrade it threw me back to the index page. And now I can not get to any admin page. &lt;br /&gt;&lt;br /&gt;  When I click the login link, or try to go to any admin page, the site serves up the main index page and the URL is weird. For example, the login URL is http://example.com/blog/wp-login.php. However, clicking on that results in getting the main page and the URL shows as http://example.com/blog/wp-login.php/. Obviously, there is no directory named wp-login.php on the site. I have no idea where that is coming from.&lt;br&gt;
&lt;br&gt;
Stuff I tried so far...&lt;br&gt;
&lt;br&gt;
1. Completed upgrade via ftp. It made no difference&lt;br&gt;
2. I&apos;ve checked for rogue .htaccess files that could be redirecting  - don&apos;t see anything&lt;br&gt;
3. Checked wp-config.php - it looks fine.&lt;br&gt;
4. Checked dB options table for unusual entries - it all looks fine.&lt;br&gt;
5. Checked theme directory - no files were changed yesterday.&lt;br&gt;
6. Deleted WPAU directory from plug-ins folder.&lt;br&gt;
&lt;br&gt;
I haven&apos;t got anything useful from the Wordpress.org forums yet, so I&apos;m trying here. I know I can just wipe the site and start over with a backup of the dB, but that would be admitting defeat. And I&apos;m not ready to do that yet.&lt;br&gt;
&lt;br&gt;
Does anybody have any ideas?</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2008:site.103582</guid>
		<pubDate>Mon, 06 Oct 2008 16:54:49 -0800</pubDate>
		<dc:creator>COD</dc:creator>
		
			<category>wordpress</category>
		
			<category>resolved</category>
		
	</item> <item>
		<title>By: Wild_Eep</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house#1499752</link>	
		<description>Backup your third party plugins, then delete them from the plugins folder. Then try to login again.&lt;br&gt;
&lt;br&gt;
WPAU is great, when it works.  It has gotten better in recent versions, but it can still be a pain.&lt;br&gt;
&lt;br&gt;
//I wish WP would just add auto-updating.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.103582-1499752</guid>
		<pubDate>Mon, 06 Oct 2008 18:11:47 -0800</pubDate>
		<dc:creator>Wild_Eep</dc:creator>
	</item><item>
		<title>By: mdavis1982</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house#1499824</link>	
		<description>Isn&apos;t the login page located at http://example.com/blog/wp-admin/ ?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.103582-1499824</guid>
		<pubDate>Mon, 06 Oct 2008 19:54:41 -0800</pubDate>
		<dc:creator>mdavis1982</dc:creator>
	</item><item>
		<title>By: COD</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house#1499836</link>	
		<description>That would get you there too - on a properly working site. On my site, that URL also gets you the main index page.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.103582-1499836</guid>
		<pubDate>Mon, 06 Oct 2008 20:09:39 -0800</pubDate>
		<dc:creator>COD</dc:creator>
	</item><item>
		<title>By: COD</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house#1499841</link>	
		<description>Deleting all the plug ins did not make a difference.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.103582-1499841</guid>
		<pubDate>Mon, 06 Oct 2008 20:15:59 -0800</pubDate>
		<dc:creator>COD</dc:creator>
	</item><item>
		<title>By: Solomon</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house#1500010</link>	
		<description>WPAU makes a backup of the index.html file in the example/com/blog directory called (I think) index.htm.bak. Try renaming it to index.htm?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.103582-1500010</guid>
		<pubDate>Mon, 06 Oct 2008 23:20:02 -0800</pubDate>
		<dc:creator>Solomon</dc:creator>
	</item><item>
		<title>By: Hanni</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house#1500053</link>	
		<description>Can you try moving everything but wp-content and wp-config.php to another directory (such as &quot;old&quot;), renaming /plugins and then re-uploading everything else? (backing up the db first would be a good idea just in case).</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.103582-1500053</guid>
		<pubDate>Tue, 07 Oct 2008 02:40:36 -0800</pubDate>
		<dc:creator>Hanni</dc:creator>
	</item><item>
		<title>By: COD</title>
		<link>http://ask.metafilter.com/103582/Is-there-a-Wordpress-expert-in-the-house#1501883</link>	
		<description>Now that I fixed it I thought I would put the solution here in case somebody else end up here with the same problem.&lt;br&gt;
&lt;br&gt;
Wordpress Auto Update apparently did two things that hoarked my site. It put a .htaccess file in the root public_html directory that was causing the weird redirect, and it changed the permissions on the entire /blog directory to 777. When I blew away the .htaccess file I started getting error messages trying to access the log in screen. The error log indicated that WP didn&apos;t like the permissions, so I changed it back to 755 and all is well.&lt;br&gt;
&lt;br&gt;
I won&apos;t be using WPAU anymore though. Something that blows up site up that bad on failure is not something I want to deal with. &lt;br&gt;
&lt;br&gt;
Thanks for the attempts at helping.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2008:site.103582-1501883</guid>
		<pubDate>Wed, 08 Oct 2008 14:04:08 -0800</pubDate>
		<dc:creator>COD</dc:creator>
	</item>
	</channel>
</rss>
