If the user clicks the edit link for a node whose language is different from the current interface language of the user in the Content page (admin/content), the interface language does not change when the edit page loads. It causes problems with references.

Members fund testing for the Drupal project. Drupal Association Learn more

Comments

C. Lee’s picture

I'm not good at English, so I include screenshots describing the problem:

screenshot 1

screenshot 2

Maybe i18n is not to blame, and someone can let me know how to change the interface language via redirection (using theme or other modules). I don't want the interface language and the content language differ in my site.

C. Lee’s picture

Title: "Switch interface for translating" should work with admin/content » "Switch interface for translating" does not work with admin/content
C. Lee’s picture

Version: 7.x-1.4 » 7.x-1.x-dev
Jose Reyero’s picture

Status: Active » Postponed (maintainer needs more info)
Jose Reyero’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Dropped that option so this is not needed anymore, see #1551688: Drop 'Switch interface for translating' option (Reconsider)

pascalduez’s picture

Status: Closed (won't fix) » Active

Hi,

well, I don't fancy re-opening old issues but I'm a bit puzzled here.
The behavior described in #1 is still well alive I'm afraid, and actually really confusing for the users/editors.

The behavior of the edit and delete links in /admin/content is different from all other places. They link to the node without switching the interface language, they keep the current language.
While the title link is switching.

If I am on /node/[nid]/translate then both title and edit links are switching language.

The non-switching edit/delete links are actually causing problems, with for instance a taxonomy widget with translated terms. If interface language != node language, then it is reset to none.

Am I missing something ?

Jose Reyero’s picture

Status: Active » Closed (won't fix)

This is some inconsistency in Drupal core (Content translation), so you can file an issue for it.