Support » Fixing WordPress » Briefly unavailable for scheduled maintenance

  • Resolved joelgomez


    Briefly unavailable for scheduled maintenance. Check back in a minute.

    That’s the legend I get when trying to enter into my wp site. I “accidentally” clicked the “upgrade automatically” button (wp 3.0)… and when I say “accidentally”, it means I HAVE NO BACKUP of my site!!!

    Should I shot myself? Any help will be greatly appreciated. Thanks.

Viewing 15 replies - 1 through 15 (of 32 total)
  • OK, I don’t understand… now I’m seeing my site again!!! Have no idea of what happened!!!

    BUT, when I try to access the dashboard, I get the following error:

    Fatal error: Cannot redeclare wp_load_image() (previously declared in /home/abogangster/ in /home/abogangster/ on line 168

    The same just happened to me. Please update this post if you can fix it. Thanks!

    My site is working fine, but I can not edit it, since I have no access to the Dashboard anymore.

    Fatal error: Cannot redeclare wp_load_image() (previously declared in /home/abogangster/ in /home/abogangster/ on line 168

    Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    Try manually upgrading. Right now, the thought is you’re missing files.

    Ipstenu, does that mean manually uploading (ftp) and overwriting all the files? Any other prior steps or things that we should have in mind to avoid having a worst result?

    does that mean manually uploading (ftp) and overwriting all the files


    Any other prior steps or things that we should have in mind to avoid having a worst result?

    Backup your database
    Deactivate all plugins
    Switch to the default theme

    How can I deactivate all plugins and switch to the default theme if I do not have access to the dashboard?

    Thanks in advance Esmi.

    Switch to the default theme by renaming your current theme’s folder using FTP (or use whatever file management application your host provides)

    Reset the plugins folder by FTP or phpMyAdmin.

    Thanks esmi, I’m in the process of backing up the entire site.

    Just to be sure, the order in which I should proceed is the following?

    1st step: Backup your database
    2nd step: Deactivate all plugins
    3rd step: Switch to the default theme
    4th step: Manually uploading (ftp) and overwriting all the files

    Am I right?

    I don’t know if I could really recommend this as a standard procedure, but since I was free to crash and rebuild my own websites, I just ripped through a couple of these upgrades fast and got stuck like this on the third upgrade, and fixing it was a piece of cake.

    I just ran

    And that took care of it. (substitute your own URL)

    I could see the files for the upgrade were in my wp-content/upgrade
    directory, so when I ran update-core.php, it ran like lightening and I had a login screen.

    From there, I just had to follow the normal instructions you get when you do this upgrade–that is, edit wp-config.php and add the specified line for security, remove blogs.php, and edit .htaccess appropriately.

    Worked great. I hope this helps and does not hurt anyone.


    I have to apologize. I spoke too soon. Running the update-core.php helped, but then when I logged in, I was taken to the dashboard where I saw an error message saying the upgrade had failed.

    From there, I merely had to click the “Re-install Automatically” button. From there, things went well, and I had my installation updated and running.

    I feel a bit better about the upgrade as it involved a complete re-installation.

    All in all, the upgrade still went pretty fast and easily, even with the glitch 🙂


    dandik, did those steps caused your site to be started from cero? I mean, did you loose everything (files, posts, etc.) or everything went back as it was before the crash?

    Another note:

    Updating WPMU 2.9.2 to 3.0 was a piece of cake on Linux where I had full control. Upgrading my one site that was on a C-panel setup posed one slight pain in the rear, but it was not difficult to solve it. The only question is whether I’m really comfortable with the solution.

    Upon upgrading, I was told to install the nonce line into wp-config.php.
    The problem I ran into is that when I logged into C-panel to administer my web environment, functionally my login (internally my Linux login) was different from the login that the webserver runs under. That means files created by the wordpress-mu environment was, say, “apache” while I was logged as “dan”.

    Solving the problem involved renaming wp-config.php to wp-config.old and then copying it back to wp-config.php. That made wp-config.php owned by “dan”, and now I could edit it. However, that also means “apache” may not be able to edit the file later.

    Just a hiccup you might run into along the way.


    See Manual Update toward the bottom of this page.

    I followed last suggestion and now Im worst than ever, I can’t see my site anymore!

    Error establishing a database connection
    This either means that the username and password information in your wp-config.php file is incorrect or we can’t contact the database server at This could mean your host’s database server is down.

    Are you sure you have the correct username and password?
    Are you sure that you have typed the correct hostname?
    Are you sure that the database server is running?

Viewing 15 replies - 1 through 15 (of 32 total)
  • The topic ‘Briefly unavailable for scheduled maintenance’ is closed to new replies.