WordPress.org

1. oceanofp
   Member
   Posted 2 years ago #

   I've never had a problem doing automatic updates, but I just did an automatic update from version 2.7.1 to version 2.8 and my site crashed with this error:

   Warning: main(/home/xxxxxx/public_html/wp-includes/pomo/mo.php) [function.main]: failed to open stream: No such file or directory in /home/xxxxxxx/public_html/wp-settings.php on line 307

   Warning: main() [function.include]: Failed opening '/home/xxxxxxx/public_html/wp-includes/pomo/mo.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/xxxxxxx/public_html/wp-settings.php on line 307

   Fatal error: Cannot instantiate non-existent class: translations in /home/xxxxxxx/public_html/wp-includes/l10n.php on line 408

   Anyone have an idea on this? Really could use some help please.

2. alfred3x
   Member
   Posted 2 years ago #

   I got the same issue. *VERY* disappointed no one has helped you out on this. Googling the error brings up a metric assload of other sites with the same error. Some of them are STILL stuck with this.

   Have you been able to resolve the issue?

3. whooami
   Member
   Posted 2 years ago #

   you can resolve the issue by uploading the missing file(s).

4. alfred3x
   Member
   Posted 2 years ago #

   OK, here's what happened. I upgraded from 2.7.1 to 2.8.4 on my dev box. It went well. I committed the changes to Subversion, and updated the blog on our staging server. That's when I got the error.

   I found another post on this forum referencing the missing file. It said all the files hadn't been copied over. The penny dropped: there were some new files in the update on dev, which weren't versioned in Subversion; so they didn't get copied to staging.

   I went through the blog directory adding any unversioned files to the repo. Commit on dev. Update on staging, and all is better.

   When I updated on prod it went smoothly.

Topic Closed

This topic has been closed to new replies.