Admin section always in English after migration

[amarok]

Hello,
I have made my first WP site migration to ClassicPress, but I encountered an issue with switching the CP language. I have also installed and activated the Use WordPress Language Packs plugin.

Expected behavior

Settings → General → Site Language, when switching a language the whole CP admin should be in selected language. I have tried with Czech and German and Spanish, each language gets installed (Dashboard → Updates) but the admin section stays always in English. Only when I visit the site the top admin bar is in the selected language.

Current behavior

Only when I visit the site the top admin bar is in the selected language.

Steps to reproduce

The migrated site is on my localhost, so I can’t share a link

Any help would be appreciated, thanks.

[Guido07111975]

Hi,

ClassicPress is (fully) translated in English (GB), Chinese, Dutch and German. So you can only select those languages, besides default English (US).

Where did you get the Use WordPress Language Packs plugin? Cannot find it.

Guido

[amarok]

I have migrated a WP site which was in Czech and after the migration I still could select all languages which were available in WordPress before. But none of that language is working, the admin page is always completely in English. So that’s the main issue I have and I don’t know what to do about it. Do you know if I can remove all translations, maybe through an SQL command in the database?

The plugin is mentioned on page ClassicPress Localization | ClassicPress in section “What if I want to use ClassicPress with another language?”. So I simply searched for it and it’s on GitHub. GitHub - ClassicPress-research/use-wp-language-packs: ClassicPress EXPERIMENTAL plugin: Use WordPress translations for locales where ClassicPress doesn't provide official translations.
So I installed that plugin to see if it fixes the problem, but no

[ElisabettaCarrara]

The issue is that the list that WP supplies is not what CP supplies as per language packs as of now. I am working to port over the most used imports from WP in batches of 5, then I will slowly put up all the other locales.

next week I will have 3 exams at a school I am attending so it will be hectic - but the first five will be up within next Sunday (Feb., 16th).

Then those imported will be added as “rolling” (uncompleted locales) to ClassicPress since during last meeting we decided that having a rolling model might suit us better, but this has to be set up since it complicates the release process and I have to see in Crowdin if it is possible to do so without issues.

[Guido07111975]

I have just installed the Use WordPress Language Packs plugin, selected čeština as language (Settings > General), and it does import the WP translation files. Language changes to čeština. So the plugin still works.

[ElisabettaCarrara]

@Guido07111975 the plugin is an inheritance - early version 1 before the i18n team we used it as a temporary replacement and can still be used because it never stopped working.

Thanks for providing the correct link to it. I am going to write an updated article here on the forums listing all notable things i18n and include that too so that being mentioned in a comprehensive article I can also provide a tutorial to use it.

[amarok]

UPDATE: Thanks.
I fixed it by disabling the Language Packs plugin to get back to basics. I have also deleted all translations from /wp-content/languages, then I logged out and logged in, I can now see only the CP-available languages, so that’s fine. CP has pulled the base translation files into /wp-content/languages

• admin-de_DE.po
• admin-de_DE.mo
• de_DE.po
• de_DE.mo

and everything works now as expected. Sorry for the confusion, I had to edit my answers now because I saw that this fixed my issues.

[amarok]

OK, thanks for help, I fixed it now! (by deleting the whole languages folder content)

[amarok]

Thanks for your effort and good luck with your exams