New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend-Language for plugins changes when working on multi-language content #6539

Open
didierCH opened this Issue Oct 8, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@didierCH

didierCH commented Oct 8, 2018

We have a Django-CMS 3.5.2 installation with languages German and French. When we work on french content the language of the plugings switches to french too (Backend stayes in German). See picture below. That behaviour is not desired. In Django-CMS 3.4.x I hadn't that problem. The user settings home > cms > User-Settings > Language are set to German.

Is there a new setting or does I overlook something?

Kind regards,
Didier

  • Python version: 3.5.3
  • Django version: 1.11.17
  • django CMS version: 3.5.2

language-problems

@didierCH didierCH changed the title from Backend-Language (Toolbar, etc.) changes to french when working on french content to Backend-Language for plugins changes when working on multi-language content Oct 18, 2018

@didierCH

This comment has been minimized.

didierCH commented Oct 18, 2018

Okay. I finally did a test with Django-CMS 3.4.6 and 3.5.2. With Django 3.4.6 I don't have that issue. If you choose a language in "User Settings" as your default language, the buttons, etc in the plugins will be properly displayed in the selected language. In Django-CMS 3.5.2 the plugin controlls are rendered in the language of the page (eg. fr, de, en, etc) rather than in the language of the Django-CMS user as set in the "User Settings".

@didierCH

This comment has been minimized.

didierCH commented Oct 18, 2018

Question: is that some sort of a regression or a feature?

@benzkji

This comment has been minimized.

Contributor

benzkji commented Nov 13, 2018

I did have this issue, but found out that adding the admin urls to the i18n_patterns (as the cms urls), it worked, but not if the admin was not "i18n'ed". didnt find the time to find out why, but you might try it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment