Make WordPress Core

Opened 15 years ago

Closed 15 years ago

Last modified 9 years ago

#9846 closed defect (bug) (duplicate)

incorrect permissions set during WP upgrade

Reported by: ryanhellyer's profile ryanhellyer Owned by:
Milestone: Priority: high
Severity: major Version: 2.8
Component: Upgrade/Install Keywords: reporter-feedback
Focuses: Cc:

Description

On installing WordPress 2.8 Beta 1 the following error was displayed:

Fatal error: Class 'Translations' not found in G:\xampplite\htdocs\wordpress2\wp-includes\l10n.php on line 379

On downgrading to WordPress 2.7.1 the problem was corrected. I tried re-upgrading to 2.8 and the same problem occurred, downgrading to 2.7.1 again fixed the problem.

Change History (12)

#1 @azaozz
15 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Sounds like you're not uploading all the files. Class Translations is defined in wp-includes/pomo/translations.php.

#2 @ryanhellyer
15 years ago

Oops! My bad.

It seems the zip file was corrupted. Not only that, but my ISP seemed to have cached the freakin' corrupted file, so whenever I download it the zip was corrupted. I got someone else to download it and email it to me and it now works perfectly :)

#3 @ryanhellyer
15 years ago

Actually ... I sent a copy of 2.7.1. I can install 2.8 on a separate install, but when I try to use it on my existing installation it spits out the error above :( I'll keep testing and see if I can figure out if this is a real bug or not.

#4 follow-up: @azaozz
15 years ago

Perhaps delete wp-admin and wp-includes to make sure all files are uploaded properly.

You can always download the latest trunk at the bottom here: http://core.trac.wordpress.org/browser/trunk

#5 in reply to: ↑ 4 @ryanhellyer
15 years ago

Thanks.

I'm guessing one of my local files was corrupted or something like that, and overwriting it doesn't seem to help. I now have a replica of my WP installation (which works with 2.8 beta 1) running in a separate folder with the same database, same theme, same plugins etc. running as on the one which doesn't work.

#6 @Denis-de-Bernardy
15 years ago

  • Milestone Unassigned deleted

#7 @ajslater
15 years ago

  • Component changed from General to Upgrade/Install
  • Milestone set to 2.8.1
  • Priority changed from normal to high
  • Resolution invalid deleted
  • Severity changed from normal to major
  • Status changed from closed to reopened
  • Version set to 2.8

upon automatic upgrade from 2.7 to 2.8 the directory wp-includes/pomo has permission 0700 making it unreadable by the websever (lighthttpd) on ubuntu linux.

[11-Jun-2009 06:24:01] PHP Warning: include_once() [<a href='function.include'>function.include</a>]: Failed opening '/usr/local/share/wordpress/wp-includes/pomo/mo.php' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /usr/local/share/wordpress/wp-settings.php on line 307
[11-Jun-2009 06:24:01] PHP Fatal error: Class 'Translations' not found in /usr/local/share/wordpress/wp-includes/l10n.php on line 408

Which leads to a fatal error and no blog.

The workaround is easy, chmod 755 on wp-includes/pomo as the files inside the directory are readable.

I suggest you look into your install zip

#8 @dd32
15 years ago

  • Keywords reporter-feedback added

Every other folder is created with the proper filesystem permissions i guess?

#9 @Denis-de-Bernardy
15 years ago

  • Summary changed from "Fatal error: Class 'Translations' not found in ... wp-includes\l10n.php on line 379" to incorrect permissions set during WP upgrade

#10 @ryan
15 years ago

The fix for #10170 might help here if the direct filesystem is being used.

#11 @dd32
15 years ago

  • Resolution set to duplicate
  • Status changed from reopened to closed

The fix for #10170 might help here if the direct filesystem is being used.

I think so..

I'm going to close this as a duplicate of that assuming it was the same issue.

reporter(s): If you still have the same issues, please re-open with details on your server setup/config and versions affected (ie. 2.8.2/3/4 shouldn't have the bug anymore due to the other ticket)

#12 @DrewAPicture
9 years ago

  • Milestone 2.8.5 deleted
Note: See TracTickets for help on using tickets.