Feature #66155
open
Backend display of localized records
0%
Description
If you translate a category the translated cat is not shown in the category list of another language.
If you translate aacat, in the database table you see a new category - but not a translated one.
So it is not possible to assign categories whith / or to translations.
IMHO a big problem.
Updated by Mathias Schreiber over 9 years ago
- Tracker changed from Bug to Feature
This is how the entire core works since.... well... ever.
You will always see the original version of a record, because there is no language switch in the BE.
I'm changing this to a feature.
Updated by Mathias Schreiber over 9 years ago
- Complexity changed from medium to nightmare
Updated by Andrea Herzog-Kienast over 9 years ago
I don't agree with you. Please translate a category and take a look in the database. A new cat will be shown in the database, but nowhere else. And so it is not usable. So this is not a feature - it is a bug.
Updated by Mathias Schreiber over 9 years ago
This has nothing to do with agreeing or disagreeing.
I would really favor if you read my entire reasoning.
Steps to understand:
Translate a page, go to any Content Element, find the header field, click the Link icon.
The page you link to is always the one in the default language.
- Category UID 2 is in default language
- You translate it via an overlay, the overlay gets the UID 3
- Since it's an OVERLAY, all relations you set need to be kept to UID 2
This is how translation overlays work at the moment:
If a page gets shown in default language, thus all relations on that page are also set to the default language.
If a page then gets overlaid with a different language, each and every relation will pick the default relation and overlay that with the current language.
It's about referential integrity.
Updated by Mathias Schreiber over 9 years ago
Followup:
The FEATURE is to make the translated category show up.
In order to do that, you need a switch to actually change the language.
A translated record does not exist.
So what you want to have is the possibility to show the language overlays of the records in default language - hence: Feature.
Updated by Xavier Perseguers over 8 years ago
Discussing this with Andrea. I agree this is something that would help a lot editors and a feature editors are actually certainly expecting. So when showing a translated record in say sys_language 2, and a category exists in sys_language 2, it would be really logical and user friendly to show the category in that language instead of the default language, regardless of the user language in use in the Backend, these are 2 different things.
Updated by Andrea Herzog-Kienast over 8 years ago
Thank you Xavier.
The differrence between a bug and an expected feature is something totally different from a devs point of view and not easy to understand.
So if this is not a bug but a feature this will not come up to the core in 6 and 7 - even if there would be a patch. Am I right?
Updated by Susanne Moog about 6 years ago
- Subject changed from Categories and localisation to Backend display of localized records
The feature should be more complete: not only categories should be shown with overlays according to the current context, that's true for all localizable records (page tree or content elements for example) - as it would be both logical and more usable for a chinese editor to see pages to link in chinese instead of - because it's default - german for example.
Updated by Susanne Moog about 6 years ago
- Has duplicate Bug #68177: Wrong Categories on pages with pages_language_overlay added