WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#29281 closed defect (bug) (fixed)

Bug with changing the language in the "General settings".

Reported by: daniluk4000 Owned by: ocean90
Milestone: 4.0 Priority: normal
Severity: normal Version: 4.0
Component: I18N Keywords:
Focuses: Cc:

Description

If we change the language (in the example, English to Russian) notification will be on the old language. I think this is a bug, otherwise, correct me.

Attachments (1)

2014-08-20 21-45-14 Screenshot.png (7.6 KB) - added by daniluk4000 6 years ago.

Download all attachments as: .zip

Change History (5)

#1 @daniluk4000
6 years ago

  • Keywords needs-patch added

If we change the language in General Settings*

#2 @ocean90
6 years ago

  • Component changed from Options, Meta APIs to I18N
  • Keywords needs-patch removed
  • Milestone changed from Awaiting Review to 4.0

This is currently fixed in my patch for #15677.

#3 @ocean90
6 years ago

  • Owner set to ocean90
  • Resolution set to fixed
  • Status changed from new to closed

In 29630:

Language packs: No WPLANG anymore.

  • The WPLANG constant is no longer needed. Remove define('WPLANG', ); from wp-config-sample.php. Populate WPLANG option based on the WPLANG constant. When get_option('WPLANG') is an empty string it will override WPLANG.
  • Introduce translations_api() which is available to communicate with the translation API. Move translation install related functions to a new file.
  • Replace mu_dropdown_languages() with wp_dropdown_languages(). wp_dropdown_languages() is now populated by the translation API.
  • Remove wp_install_load_language() and allow load_default_textdomain() to switch a core translation.

fixes #13069, #15677, #19760, #28730, #29281.

#4 @ocean90
4 years ago

In 39122:

I18N: Show "Settings saved." in the correct language after switching the site language.

This simplifies the logic by comparing get_user_locale() before and after an settings update.

Props swissspidy, ocean90.
See #29783, #29281.
Fixes #38482.

Note: See TracTickets for help on using tickets.