Whoops! Lost Initial Blog after upgrade…

So, here I go diving into waters that are apparently too deep for me.

I upgraded manually to 2.8.2 and upon doing so you can no longer see the main site of the wordpressmu install ie (http://domain.com). Instead it takes you to the wordpressmu login page.

All blogs are still there and if you go to any of the subdomains, (http://subdomain.domain.com) they all work fine. This is good as this is where all my clients reside.

When I log into wordpressmu, everything is still there and intact. The main blog still shows up in the backend, but when I try to go to the site I am always brought back to the admin interface (as I’m already logged in).

Geez, I’m a n00b! Anyone got some suggestions on what I can do to fix this? Thanks in advance

  • Mason
    • DEV MAN’s Sidekick

    If you hit the main blog at http://knowledgefranchise.com you get redirected to this link:

    http://knowledgefranchise.com/wp-login.php?redirect_to=http%3A%2F%2Fknowledgefranchise.com%2Fwp-admin%2F

    If you’re logged in, it takes you to the admin page, just like the redirect link says it will.

    If you go to one of the subdomains:

    http://hackintosh.knowledgefranchise.com

    http://truthtransforms.knowledgefranchise.com

    you see the site as you expect them to be.

    Thanks again!

  • Mason
    • DEV MAN’s Sidekick

    Site-wide there are 27 plugins installed and available. On the blog mentioned above there are 9 that are active.

    Would deactivating these plugins be enough to troubleshoot or do I need to delete (or move) them all?

    Here’s the list of active ones:

    -Akismet

    -All in One SEO Pack

    -Easy AdSense

    -Google Analytics for WordPress

    -Google XML Sitemaps

    -Reveal IDs for WP Admin

    -Unfiltered MU

    -Viper’s Video Quicktags

    -WP Super Cache

    I also have several mu-plugins (18 of them) installed.

    Thanks again.

  • Andrew
    • Champion of Loops

    The only one I’m not sure about is this one:

    Reveal IDs for WP Admin

    That’s just because I’ve never heard of it so I don’t know what it does.

    I’d try renaming mu-plugins to something like mu-plugins-temp. If the problem goes away then it’s one of the plugins in there.

    Thanks,

    Andrew

  • Ovidiu
    • Code Wrangler

    otherwise seeing your .htaccess might be interesting and one more question: did you use the "Dashboard Blog" option under site admin => options?

    That might explain it if you have mistakenly set the main blog as the dashboard blog? I heard there is an automatic redirect to the back end, as the dashboard blog isn’t meant to be viewed, its just for the back end…

    just some wild guesses here but its worth checking :slight_smile:

  • Mason
    • DEV MAN’s Sidekick

    Hey Andrew,

    I changed the mu-plugins to mu-plugins-temp like you recommended:

    no change

    I then deactivated all plugins associated with the domain blog account:

    still no change.

    It continually re-directs the main page to the wp-admin.php and if you are not logged in, it asks you to log in.

    Any other ideas?

    This only occurred after I manually upgraded from 2.8.1 to 2.8.2. I downloaded the zip file, extracted it and then copied everything from wp-admin, wp-includes, and then most of the root directory files.

    From my original install the wp-contents folder, .httacces, and wp-config.php were all left untouched. Did I miss a step? Trust me… with me, anything’s possible…

  • Mason
    • DEV MAN’s Sidekick

    My dashboard blog setting is blank. I’ve always had it this way, but that’s a good thought.

    Here’s the contents of the .htaccess file:

    DirectoryIndex index.html index.php

    RewriteEngine On

    RewriteBase /

    #uploaded files

    RewriteRule ^(.*/)?files/$ index.php [L]

    RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*

    RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]

    # add a trailing slash to /wp-admin

    RewriteCond %{REQUEST_URI} ^.*/wp-admin$

    RewriteRule ^(.+)$ $1/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]

    RewriteCond %{REQUEST_FILENAME} -d

    RewriteRule . - [L]

    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]

    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]

    RewriteRule . index.php [L]

    <IfModule mod_security.c>

    <Files async-upload.php>

    SecFilterEngine Off

    SecFilterScanPOST Off

    </Files>

    </IfModule>

    Yeesh…

  • Andrew
    • Champion of Loops

    Nothing really seems off with your .htaccess file. Have you tried renaming the plugins directory just to make sure it’s not one of those plugins?

    Other than that my only suggestion is to have someone take a look at your site. Hopefully someone else will have more suggestions though.

    Thanks,

    Andrew

  • argh2xxx
    • The Incredible Code Injector

    You can do this!

    Back up your Databases and files so you can revert to the original state whenever the need arises. Reinstall wpmu 2.8.2 fresh. Then modify your wp-config.php to point to the multidb’s global db. Get the multidb files into wp-content/ directory again. Make sure the settings are still correct inside multidb files.

    Though don’t listen to me if you think that this suggest will make your problem worse.

    Please do not blame me for this suggestion. It’s your own risk when trying this suggestion. Good Luck!

  • Mason
    • DEV MAN’s Sidekick

    Thanks for the encouragement!

    I have tried changing all plugin (mu and otherwise) folders and there’s no difference. The good thing is that at least the "domain.com" site is my own and my users don’t need access to it. The other sites all use domain mapping and can still login to the backend of their sites. In other words, their pages are unaffected (whew!).

    I may try your suggestion later tonight, argh2xxx (appropriate name for me right now by the way) as I don’t see any other options. No worries, no blame will be thrown your way should this not work and the entire internet (or the small portion I administrate) come crashing down. Thanks or the tip!

    I also have the following error in the log file in the root wordpressmu directory:

    [16-Jul-2009 21:43:36] PHP Warning: gzinflate() [function.gzinflate]: data error in /home/mark/public_html/wp-includes/http.php on line 1787

    [16-Jul-2009 21:43:36] PHP Warning: gzuncompress() [function.gzuncompress]: data error in /home/mark/public_html/wp-includes/http.php on line 1792

    I figure this has something to do with the update process not working correctly, but this happened before I did the manual upgrade to 2.8.2

  • Ovidiu
    • Code Wrangler

    I had a slightly similar problem with a wordpress installation. I had installed a plugin that offered a login widget where I had set a url to redirect to after logging in. after deactivating and removing the plugin, that setting still persisted. It seems like that plugin set this redirect after login setting in the options table and then forgot about it.

    can you search via phpmyadmin for %redirect% inside your wp_1_options table?

    just satisfy my curiosity :slight_smile:

  • Mason
    • DEV MAN’s Sidekick

    Ovidiu,

    I took a look in the wp_1_options table and did find two keys that had %redirect%, but they both appear to be entries that came with the new version of wordpressmu. The option value of both includes information about the reason for the 2.8.2 (Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.)

    Still looking for at "options". Thanks for the thought!