WordPress.org

Make WordPress Core

Opened 9 years ago

Closed 9 years ago

Last modified 6 years ago

#2887 closed defect (bug) (wontfix)

Load default localization domain before load plugins

Reported by: Sewar Owned by: Sewar
Milestone: Priority: normal
Severity: normal Version: 2.0.3
Component: General Keywords: plugins l18n bg|has-patch bg|needs-testing
Focuses: Cc:

Description

Some plugins uses localization after loaded (like Widgets), but default domain loaded after loading plugins. So, when this plugins try to use localization the text will not be translated and no error will occur.

Attachments (1)

wp-settings.php.diff (1.0 KB) - added by Sewar 9 years ago.
Load default localization domain before load plugins

Download all attachments as: .zip

Change History (8)

@Sewar9 years ago

Load default localization domain before load plugins

comment:1 @Sewar9 years ago

  • Keywords bg|has-patch bg|needs-testing added
  • Owner changed from anonymous to Sewar

comment:3 @ryan9 years ago

We load the textdomain after plugins are loaded so that plugins have the chance to modify the locale. This change might break some localization plugins.

Plugins shouldn't be invoking any gettext until after the init action.

comment:4 @Sewar9 years ago

ryan: You're right. Widgets plugin start with calling "register_sidebar_widget" function which uses gettext. Is put this calls in "init" action will fix this bug? i hope. If it's yes i will update Widgets patch to do this.

comment:5 @Sewar9 years ago

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

comment:6 @anonymous9 years ago

  • Milestone 2.0.4 deleted

Milestone 2.0.4 deleted

comment:7 @Denis-de-Bernardy6 years ago

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