WordPress.org

Ready to get started?Download WordPress

Forums

[closed] Ran auto update for 3.1 and now site doesn't work (deleted mait mode file) (59 posts)

  1. AardvarkGirl
    Member
    Posted 3 years ago #

    I was just working with this site yesterrday. Sat down to continue the work and saw the update. Ran the update, it went into maintenance mode - fine, ok. Killed that maint file on the server, logged onto the server to give the directory full permissions. Went back into my WP admin and ran the auto update again. Said it completed fine but when I went to the front end it just does NOTHING (in IE).

    Firefox gives me this error... "Firefox has detected that the server is redirecting the request for this address in a way that will never complete."

    I tried running the auto install a few times, all 'completed' - then I even went in and reverted back to the stock 2010 theme. Still nothing.

  2. AardvarkGirl
    Member
    Posted 3 years ago #

    Not sure if this additional info helps. As of yesterday I was 'up to date' with the most current version.

    This site is in a sub directory, and was moved there after it was installed - but I'm pretty sure I've run updates since then.

  3. esmi
    Forum Moderator
    Posted 3 years ago #

    Try:
    - switching to the Twenty Ten theme by renaming your current theme's folder in wp-content/themes using FTP or whatever file management application your host provides. You may need to access /wp-login.php to get this to kick in fully.

    - resetting the plugins folder by FTP or phpMyAdmin.

    - re-running the upgrade manually using /wp-admin/upgrade.php.

  4. AardvarkGirl
    Member
    Posted 3 years ago #

    ESMI - I have full access to the server. So will go and try your suggestions.

    I was able to get the theme to change, and if I go in thru the admin, PAGES and click to 'preview' I can see the front end (in admin mode of course), and see the theme has changed.

    I will go give your suggestions a try though. In the meanwhile before you posted...

    I was going to go in and deactivate the few plug ins installed. Just out of curiousity I tried to run an update for a contact form plug in, it failed, then when I went back to view it in the plug in lists, it is totally gone. :-\ But the admin area let me deactivate all plug ins.

  5. AardvarkGirl
    Member
    Posted 3 years ago #

    ESMI - tried using FTP and could not change the plug-ins folder name to plugins.hold (or what ever it was the article suggested).

    I then went thru phpmyadmin and the setting was already a:0:{} (because as I said I was allowed to deactivate all my plug ins).

    Still no site on the front end. :-(

  6. AardvarkGirl
    Member
    Posted 3 years ago #

    Ok, just for sh*ts N giggles I ran the auto update on our wordpress test site - same exact server but not running in a sub folder - and the result is the same.

    The site is dead. :-\

    Site A had minimimal plug ins installed and was running on a TemplateMonster theme.

    Site B was had 1 plug in (demo data) and was running on a 2010 child theme.

    *sigh*

    Site B was just auto upgraded (same server settings etc) from 0.4 to 0.5 not too long ago and everything went fine, so I don't get how it could be a permissions issue (just talking out loud).

  7. AardvarkGirl
    Member
    Posted 3 years ago #

    Ok - site B... I manually downloaded and uploaded all the 3.1 files manually and still no front end of the site.

    So then I went in and killed EVERYTHING. The database, all the files, and ran a totally new install on this. Created a new database, ran the install... still nothing on the front end. *sigh*

    Tried opening it in Chrome this time and got this error:

    his webpage has a redirect loop
    The webpage at http://ra-wordpress.com/ has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
    Here are some suggestions:
    Reload this web page later.
    Learn more about this problem.
    Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

  8. AardvarkGirl
    Member
    Posted 3 years ago #

    Just another update (guess I'm just talking to myself at this point)

    I totally killed site B, all 3.1 files and the database, and did a resintall from 3.05 with a brandnew database. Works like a charm, like it was before this update.

    So.

  9. krispy_b
    Member
    Posted 3 years ago #

    getting the same issues - "Firefox has detected that the server is redirecting the request for this address in a way that will never complete."

    thank god i didn't upgrade all my wordpress sites, although i've broken my most important/busy.

    You on windows server too?

  10. AardvarkGirl
    Member
    Posted 3 years ago #

    Yes... windows server.

  11. fivexs
    Member
    Posted 3 years ago #

    Same problem here with a windows server. I now have one useless site for my customer that doesn't seem to work. Any suggestions people?

  12. scythe944
    Member
    Posted 3 years ago #

    Just wanted to chime in that I have the same problem, which is also a Windows server.

    I'm trying to disable all of my plugins, but it doesn't seem to be helping so far. Guess we should all remove the latest update huh?

  13. scythe944
    Member
    Posted 3 years ago #

    All plugins disabled, reset them to Twenty Ten and still can't access the site's frontend.

    Guess I'll be restoring from a backup until a fix is provided.

  14. AardvarkGirl
    Member
    Posted 3 years ago #

    I set up a totally FRESH install with a brand new database... with a totally new directory/domain name and it still produce the same error for me.

    So plug-ins shouldn't be the issue - unless it is the plugins that come STOCK with the 3.1 download. :-\

    http://www.rastaging9.com/

  15. fivexs
    Member
    Posted 3 years ago #

    Shite. i forgot to do a backup. Any solutions people?

  16. scythe944
    Member
    Posted 3 years ago #

    I just made it work by using the following:

    http://wordpress.org/support/topic/revert-to-an-older-wordpress-version
    http://codex.wordpress.org/Upgrading_WordPress_Extended

    Basically, download 3.0.5 IIS from the release archive: http://wordpress.org/download/release-archive/

    Delete all worpress files EXCEPT for the ones described in the "Upgrading WordPress Extended" article,

    Upload the 3.0.5 IIS zip file to your server, extract the files where WordPress is installed, and visit the site to do the "database upgrade" which is actually doing a downgrade.

    I also have MySql doing backups every night and I dropped all databases and restored from 2-16-11 (because my last file backup of the server was that day, I know, I know), but that probably doesn't need to be done. In fact, I'll probably restore last nights backup now.

    That should get you back up and running.

  17. scythe944
    Member
    Posted 3 years ago #

    Yep, just restored the latest database backup and everything is exactly the way it was before the 3.1 upgrade.

    I'm sure that there will be others with this problem, as I'm sure there are a few people that host wordpress on Windows.

    How can we tell them that 3.1 seems to be broken on Windows servers?

  18. evilhare
    Member
    Posted 3 years ago #

    Well, I guess if you dont know all this stuff, you're screwed

  19. scythe944
    Member
    Posted 3 years ago #

    Know all what stuff exactly? It might be a little overwhelming for someone that doesn't work on computers very much, but if you take your time and read a little, it should be ok.

    I'm sure that since we could all still access the admin area we can upgrade to the next version that will fix this mess, so if you can just hold out for a little while, you can just upgrade to the fixed version when it comes out.

    If you can't wait, then try following my directions to fix it.

  20. esmi
    Forum Moderator
    Posted 3 years ago #

  21. AardvarkGirl
    Member
    Posted 3 years ago #

    ESMI - checked out your link....

    WINDOWS SERVERS
    Infinite redirects on IIS servers - Try using the Permalink Fix & Disable Canonical Redirects Pack

    Does this apply to a fresh, totally new install?

  22. esmi
    Forum Moderator
    Posted 3 years ago #

    It may affect all 3.1 installs.

  23. scythe944
    Member
    Posted 3 years ago #

    Since the Canonical Redirects are built in to wordpress, I'd assume that yes, it would apply to a fresh install.

    I'm not positive though. I've been using WordPress for a number of years, but I'm not that "into" the code like others.

    I just install and run the darned thing, you know?

  24. scythe944
    Member
    Posted 3 years ago #

    esmi, the link that you provided shows that windows server users should download the redirect pack: http://wordpress.org/extend/plugins/permalink-fix-disable-canonical-redirects-pack/

    However, it only says that it's compatible with WP versions up to 3.0.5.

    I guess it's ok to still try and use it on 3.1 though?

    I'll give it a shot and try upgrading to 3.1 again if you say so.

  25. esmi
    Forum Moderator
    Posted 3 years ago #

    I don't have any installs on Windows servers but the 3.1 Master List is the pooled experience of quite a few forum mods & regulars. So, yes, I'd say that it's safe to use that plugin. My guess is that the plugin's readme file just hasn't been updated yet.

  26. scythe944
    Member
    Posted 3 years ago #

    Ok cool... I'll be the guinea pig and try it out.

    I'll let everyone know if it fixed the problem for us or not.

  27. scythe944
    Member
    Posted 3 years ago #

    woohoo! looks good.

    So, for anyone that has a botched install on a Windows Server, Install the http://wordpress.org/extend/plugins/permalink-fix-disable-canonical-redirects-pack/

    Then, activate it.

    Works fine here: http://www.stignatiushickory.org

    *Edited to remove extra steps that were deemed unnecessary*

  28. esmi
    Forum Moderator
    Posted 3 years ago #

    Excellent! Thanks for the report back.

  29. scythe944
    Member
    Posted 3 years ago #

    Sure no problem. Now I'm wondering if we don't have to downgrade first though.

    If you still have access to the admin panel (by visiting your domain name and adding the /wp-admin onto it), you might be able to just install the plugin, activate it, and be ok.

    Wonder if anyone can confirm this? I really don't feel like breaking my customer's site again right now :-)

  30. scythe944
    Member
    Posted 3 years ago #

    nevermind, there's another thread with the same problem and it seems that the plugin fixes it.

    Well, there's your answer!

    Install plugin, fixed.

Topic Closed

This topic has been closed to new replies.