WordPress.org
Get WordPress

Make WordPress Core

Opened 20 years ago

Closed 20 years ago

Last modified 16 years ago

#2887 closed defect (bug) (wontfix)

Load default localization domain before load plugins

Reported by: sewar's profile Sewar Owned by: sewar's profile 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 20 years ago.
Load default localization domain before load plugins

Download all attachments as: .zip

Change History (8)

@Sewar
20 years ago

Load default localization domain before load plugins

#1 @Sewar
20 years ago

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

#3 @ryan
20 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.

#4 @Sewar
20 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.

#5 @Sewar
20 years ago

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

#6 @(none)
19 years ago

  • Milestone 2.0.4 deleted

Milestone 2.0.4 deleted

#7 @Denis-de-Bernardy
16 years ago

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