Closed blaues0cke closed 3 years ago
A working workaround for this just to remove slug
and singular_slug
. Its also possible then to delete the new generated (different) mysql table and rename the old one that still exists behind the scenes to the correct/new name.
This also occurs when the name of the content type contains a underscore (_
). So this works:
restaurantmenuitem:
name: Speisekarten-Einträge
singular_name: Speisekarten-Eintrag
and this not:
restaurant_menu_item:
name: Speisekarten-Einträge
singular_name: Speisekarten-Eintrag
I just run into the underscore issue.
Wasted some time on figuring this out.
So translations are working like a charm for this contenttype:
But when I change
slug
and/orsingular_slug
thededata
andendata
fields are now longer maintained and the locale is stored in the original fields:Details
Reproduction
1) Add this content type:
2) Add a new job 3) Change the locale 4) Edit the job title 5) The job title is changed over all locales
Expected: The locale only should be changed for the selected/active language.