error after upgrading to 3.1.2

  • Hi,

    I was working in my dashboard (3.1.1) and saw a message to upgrade to 3.1.2.

    I clicked on the auto upgrade option and it appeared to work correctly (have used this before for previous versions) but when I then tried to go to another area in the dashboard I got the following error
    Fatal error: Call to undefined function get_option() in /home/growdigi/public_html/wp-admin/admin.php on line 32

    and if I try and view the site I get:

    Fatal error: Call to undefined function wp() in /home/growdigi/public_html/wp-blog-header.php on line 14

    Can you please advise the quickest way to get my site back up, as I have already had one client call about it.

    Thank You

Viewing 5 replies - 1 through 5 (of 5 total)

  • Your upgrade did not complete successfully.
    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.

    – resetting the plugins folder by FTP or phpMyAdmin.

    – re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress.

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

    Hello.
    I’m a .net developer. I’m a 100% complete wordpress nube.
    I have a similar problem. There was an attempt to install a module and the result was a completely white screen. I can’t see or access anything else.
    It’s clear that installing the module caused the problem. As mentioned above how can I reset the modules folder by ftp?

    Thank you.

    edit…. sorry I see you added a link! doh!

    @fatscally: Your issue is unrelated. Please post a new topic in the Troubleshooting forum.

    uhmmm ok, please excuse my noobness, but your link was invaluable. Renaming the Plugins folder got the site running again. An error trap for this would be perfect.

    Thanks again.

    Thread Starter rhartland

    (@rhartland)

    Thanks for the advice guys, have got it up and running again ??

    Any tips on helping to prevent this from happening again?

    Cheers,
    Richard

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘error after upgrading to 3.1.2’ is closed to new replies.