Quantcast
Viewing all articles
Browse latest Browse all 294989

Translated string are loaded into Views UI and then saved as default language strings.

There is a problem with the Views UI when used with multilingual Drupal sites. If a view is accessed in another language then the default language the Views UI will load the translated strings if available. So far so good but when hitting the Save button those translated strings will overwrite the original strings. Thus the view in default langue now contains translated strings from the translated language.

Steps to reproduce:

1. Set up a view in a view in a multilingual Drupal, in my example I will use German (de) as default and English (en) as additional language.
2. Create a view in default language and translate a few strings into an additional language and save. E.g. the title of the View.
3. Open the View UI in the additional language, in our case English. e.g. http://[drupal_root]/en/admin/structure/views/view/[view_name]/
4. Note that views UI opens the view with the Title translated and save the view.
5. Open the view in it's default language (e.g. http://[drupal_root]/de/admin/structure/views/view/[view_name]/) and note that the original Title has been overridden.

The question arises how Views UI should handle multilingual content. Should it remember that strings are translated and save those correctly or should it always load the original strings from the beginning?

A similar situation would be the translation of the Title Label of a Content Type. In the content type UI Drupal will always load the Title Label in the content types original language no matter what language you access the UI in. Thus anything related to translation are keep separately over at translations only.

Suggested resolution:
1. Remove the translation of strings in the Views UI.


Viewing all articles
Browse latest Browse all 294989

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>