WordPress.org

Ready to get started?Download WordPress

Forums

fatal error after 3.0.5 update (13 posts)

  1. JRU
    Member
    Posted 3 years ago #

    I just did the update to 3.0.5 and I am getting this error when I try to go to my dashboard or website...

    Warning: require(/home/content/66/7213066/html/wp-includes/pomo/mo.php) [function.require]: failed to open stream: No such file or directory in /home/content/66/7213066/html/wp-settings.php on line 82

    Fatal error: require() [function.require]: Failed opening required '/home/content/66/7213066/html/wp-includes/pomo/mo.php' (include_path='.:/usr/local/php5/lib/php') in /home/content/66/7213066/html/wp-settings.php on line 82

    Please help! Thank you so much!

  2. Tara
    Member
    Posted 3 years ago #

    -make sure all files/folders got uploaded to the right location.

  3. dragonc
    Member
    Posted 3 years ago #

    There is a bug in the new version, its well covered in the forum if you read through it. One suggested fix is to change the name of the plugin folder by FTP or cpanel, then you should be able to access the site. Change the plugin folder name back after getting into admin, activate akismet and upgrade it, then reactivate the other plugins. But do read through this forum first.

  4. Andrew Nacin
    Lead Developer
    Posted 3 years ago #

    dragonc: There isn't a "bug" in the new version that would cause this. Please stop suggesting this on every 3.0.5 post on the forum. It's wrong.

    JRU: Please try a manual update of WordPress. It looks like you're missing some files. http://codex.wordpress.org/Updating_WordPress#Manual_Update

  5. JRU
    Member
    Posted 3 years ago #

    I did try to change the plugin folder name and that didn't change anything for me.

    I was actually was doing the manual update. (I am not sure if I changed the name of certain files, so I did not know if I could do the automatic update.) I tried it the manual way several times. Sometimes the 'line number' in my fatal error message would change, but I could not get it to work. After spending hours on it last night, I gave up and restored the old version I already had (3.0.4).

    At this point I am hoping the updates are not that important, that it would not 'harm' anything if I did not do them. My blog is part of my business and it was down for like 7 hours while I was trying to figure this out. I am scared to try again. :)

  6. Tara
    Member
    Posted 3 years ago #

    I manually updated from 3.0.4 to 3.0.5 with no issues. So, I wonder if there are any problems with the server.

    -try contacting the hosting provider if the database server is online / if they have any other problem at their end, or they made any changes to your account, or if there are any limitations/restrictions, etc.

  7. dragonc
    Member
    Posted 3 years ago #

    "dragonc: There isn't a "bug" in the new version that would cause this. Please stop suggesting this on every 3.0.5 post on the forum. It's wrong."

    Andrew - If its not a bug, why was a fix added via Akismet? Or is "bug" the wrong word to describe something that causes problems to so many who upgrade? I don't recall there being so many problems on previous upgrades.
    I will keep quiet from now and let others help as I am obviously posting false information and not welcome here.
    My site crashed after upgrading like many others. I followed a piece of advice which I passed on to others with the same problem, so that was obviously the wrong thing to do.
    I restored the previous version and won't upgrade again until 3.5 comes out.
    Bye

  8. westcoastmktg
    Member
    Posted 3 years ago #

    Andrew, If I can't even log into my admin area how can I change locations etc.?

    My blog is a WP free hosted blog (so I didn't see a cpanel

  9. Samuel Wood (Otto)
    Tech Ninja
    Posted 3 years ago #

    If its not a bug, why was a fix added via Akismet?

    The "fix" added via Akismet is extremely minor and only would have impacted a small handful of people. Specifically, it caused images to be incorrectly stripped out of comments for Admin and Editor level users.

    That's it. It has nothing to do with upgrading, installation, or any of the things you keep reporting it for. It's a minor issue that rarely impacts anybody at all.

    So please, if you don't know what you're talking about, then stop responding to people with incorrect information.

  10. westcoastmktg
    Member
    Posted 3 years ago #

    Otto, It doesn't feel minor to me since I'm impacted on two sites and cannot access my admin area or view my blogs

  11. Samuel Wood (Otto)
    Tech Ninja
    Posted 3 years ago #

    westcoastmktg: Yes, and I understand. However, that problem you are experiencing is not caused by a bug in WordPress, and certainly not by the bug dragonc keeps going on about.

  12. raeben
    Member
    Posted 2 years ago #

    Don't know if anyone ever resolved this issue but I just had the same problem after an upgrade. the file "mo.php" could not be found. It was supposed to be in the subdirectory "pomo" inside wp-includes.

    I could log in using ftp and so I searched and found the "mo.php" file. Instead of wp-include/pomo it was in wp-include/wp-include. I had 2 wp-includes, one nested within the other.

    Copied the nested wp-include that contained mo.php and 4 other files to my desktop and then created a directory called "pomo" in the original, outer wp-include. Did not delete the other sub "wp-include". Everything appears to be working.

    I had used an automatic install. I can't tell if this is a bug or not, but it's mighty strange.

  13. TheBrandThing
    Member
    Posted 2 years ago #

    Hi,

    I installed the new wordpress update in the my wordpress site http://www.thebrandthing.com and after that I am getting this error message "Fatal error: Call to undefined function wp() in /home/t8b2d9g6/public_html/wp-blog-header.php on line 14", whenever I am trying to launch the site or even when I am trying to signing in to the admin.

    How do I recover my site out of this problem???

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.