Closed sidedwards closed 2 years ago
This was a tricky one, due to how Craft propagates content. It assumes that if the Vizy field isn't translated, then the content should all be the same. Even though Matrix is in a similar situation to Vizy, it's much less complicated due to each block being an element - something Vizy isn't (for performance, and part of the whole deal). As such, we need to handle the inner content consolidation and propagation ourselves.
Fixed for the next release. To get the fix early, change your verbb/vizy
requirement in composer.json
to:
"require": {
"verbb/vizy": "dev-craft-3 as 1.0.9",
"...": "..."
}
Then run composer update
.
Fixed in 1.0.10
π Bug description
As the title states, when Vizy is set up as "non-translatable", localized (i.e. translatable") fields within store their values globally basis v.s per-site and content in other sites get overwritten content on save.
Additional info
1.0.9
3.7.30.1
π£ Reproduction steps
Steps to reproduce the behavior:
π¦ Expected behavior
Localized fields within non-localized Vizy blocks should store their values on a per-site basis v.s globally.
π΄ Actual behavior
Localized fields within non-localized Vizy blocks store their content across all sites.
π Resources
https://user-images.githubusercontent.com/11489608/152849074-d727bea2-78fd-4c1b-bdd6-78a163ccde58.mp4