Hi all.
I am a bit mystified about the behavior in strapi-admin when I create a new language version of an entry. (strapi v4.15.5)
I have a couple of non-language-versioned fields: text and boolean.
The text field is empty on my new entry even though it has a value on all the existing language versions. When I save, however, the value is set correctly on my new entry. Copied from the existing versions as expected.
The boolean field defaults to false similar to how the text field defaults to empty. Also despite the fact that the field is true on the existing versions of the entry.
The really “dangerous” part is that when I save my new entry, the “false” value is copied to all the existing items instead of the other way round. Even the entries that are already published.
The end result is that by clicking “new” and “save” I end up with the value “false” value being copied to all the other language versions of this item.
The problem seems even worse when draft and publish is part of the scenario. “new” and “save” on a draft version will update all my published items. So even though I never click publish, I am changing published items.
Wouldn’t it make a lot more sense if the non-language-versioned fields in the UI of the new item was prefilled with the value from one of the existing items?
Or am I thinking about this the wrong way?
Will this be better in Strapi 5? At least I assume that the draft/publish part of the problem will be solved, right?
This topic has been created from a Discord post (1228303251632422942) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord