Support » Installing WordPress » Another fatal error when upgrading to 3.2

  • I just upgraded automatically to 3.2 (and of course, did not first backup anything)… and now my site is not accessible. This is error shown:

    Warning: require_once(/home/consumer/public_html/ [function.require-once]: failed to open stream: No such file or directory in /home/consumer/public_html/ on line 145

    Fatal error: require_once() [function.require]: Failed opening required ‘/home/consumer/public_html/’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/consumer/public_html/ on line 145

    I cannot access ANYTHING.

    I do have a backup from last week.

    Any idea how to get out of this mess?



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


    Forum Moderator

    FTP into your site (or use whatever file management application your host provides) and rename the wp-content/plugins/tweet-this then see this post

    Hi Edgar

    Your problem is proably related to the plugin Tweet This – see this thread
    See the first post (re how to deactive a plugin when you can’t log in) and also read the Plugin Issues post further down the page.

    Good luck 🙂

    Edit – I took too long to post and got beaten to the punch 🙂


    I think I love you.

    The site is back.

    I am guessing since the site is back that my hosting company’s server has all the required upgrades?

    How do I uninstall tweet-this (subdirectory now renamed tweet-thiss) assuming this was the cause of the problem?

    Thanks again.




    Forum Moderator

    If the site is running correctly, then it’s reasonable to assume that upgrade was successful. You can always check by trying to re-run the upgrade via Dashboard -> Updates. If the site is up-to-date, WP won’t run the upgrade but will simply display an up-to-date message.

    You can remove the tweet this plugin by simply deleting the renamed wp-content/plugins/tweet-thiss folder. Or you can see the link I gave above for a temporary fix that will allow you to continue using the plugin. With luck, the plugin’s developer will release an update that will address the problem permanently in the near future.

    Thanks again, esmi (and ridg…)


Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Another fatal error when upgrading to 3.2’ is closed to new replies.