Ticket #9183 (confirmed Feature Request)

Opened 7 years ago

Last modified 3 years ago

Language set in user preferences can't be used as a negotiator

Reported by: spereverde Owned by:
Priority: minor Milestone: 4.x
Component: Internationalization Version: 4.3
Keywords: Cc:

Description (last modified by MatthewWilkes) (diff)

I recently tested the effect it would have on the language that is set in the user preferences (in the site setup). To my surprise I found that changing this setting doesn't change anything, with or without LinguaPlone. Even after I restart and login again all new items that I create stay in the default site language. I tested following situations on both Plone 3.2.2 and Plone 3.3rc2:

  • No LinguaPlone in the buildout
  • LP in buildout but not installed
  • LP in buildout and installed

In none of these cases did the user preferences - language setting change anything.

Change History

comment:1 Changed 7 years ago by hannosch

  • Status changed from new to closed
  • Resolution set to invalid
  • Type changed from Bug to Feature Request

This would be a feature request for LinguaPlone, which isn't part of Plone Core itself. The user specific language setting in the preferences isn't used for anything in Plone at all, it's just metadata about a user, like his location or name.

comment:2 Changed 7 years ago by WouterVH

This is not about Linguaplone

in the personalize_form there are many settings a user can set:

  • use external editor: yes/no
  • enable short id-editing: yes/no
  • select your favorite visual editor: kupu

these have real effects when editing content, so this is not just metadata about the user.

But there is confusion about this one:

  • select your preferred language

if this language-settings is just metadata, then why can you select "Language neutral?" I don't know many users who are language neutral :)

"Language neutral" seems to imply that setting this to a certain language will affect the language of the content the user is adding.

If it's just metadata who no effects on editing, it could just be called "mother language" or something.

comment:3 Changed 7 years ago by hannosch

  • Milestone changed from 3.x to 3.3

comment:4 Changed 3 years ago by MatthewWilkes

  • Status changed from closed to reopened
  • Description modified (diff)
  • Summary changed from language set in user preferences has no effect on new items? to Language set in user preferences can't be used as a negotiator
  • Version set to 4.3
  • Milestone changed from 3.3 to 4.3
  • Resolution invalid deleted

comment:5 Changed 3 years ago by MatthewWilkes

As Wouter says, this isn't LP specific. There is a workaround in the collective developer manual, but this could easily be added to core.

 http://collective-docs.readthedocs.org/en/latest/i18n/language.html?highlight=ipubaftertraversal#login-aware-language-negotiation

comment:6 Changed 3 years ago by kleist

  • Status changed from reopened to confirmed
  • Milestone changed from 4.3 to 4.x
Note: See TracTickets for help on using tickets.