Updating makes the backend display in a localized version

  • urmachtra

    (@urmachtra)


    10 years, 4 months ago

    After updating to 3.8 version the backend is displayed in a localized language version, the same as the frontend, which is not what I want.

    I find this strange as this has never happened before.

    How can I make it so that I can use the english backend as before, and continue to use my localized version of the frontend?

    I’ve been using Codestyling Localization plugin for many years to translate the themes I’ve been using.

    I have also needed to translate some words that are part of WordPress as they are used in the frontend too, and set the language code in the wp-config file. But this has never made the backend display in the localized version before.

    If I remove the language code from WPLANG in the wp-config file, then both the backend and the frontend are displayed in english.

Viewing 1 replies (of 1 total)
  • Thread Starter urmachtra

    (@urmachtra)

    10 years, 4 months ago

    I seem to have solved this by removing both the newly added and modified WordPress language files in /wp-content/languages.

    But I’m not sure if I should mark this topic as solved as I need to know why the WordPress 3.8 update makes the backend use a localized version as set for the language code in wp-config file, but was only intended for the frontend localized version.

    I have no need for translated admin section as I think it impractical. I need to have the admin section terms recognizable in the English language. Besides the prepared WordPress localized version is just partly translated.

Viewing 1 replies (of 1 total)
  • The topic ‘Updating makes the backend display in a localized version’ is closed to new replies.

Tags