Closed mattbloomfield closed 2 years ago
It shouldn't matter too much if they're strings or arrays, other than how the content is stored. When normalised (read from the database), they're sorted into nested Node Collections, which can be queried freely.
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.10",
"...": "..."
}
Then run composer update
.
I agree it shouldn't matter, but this was not normalizing them the way it did previously. Thanks for the fix!
Fixed in 1.0.11
Description
I noticed this after upgrading to 1.0.10 and it goes away if I jump back to 1.0.9.
Basically we have times where we have a vizy field nested in a vizy. In those cases, when you save those entries they are stored as strings instead of arrays.
E.g. (look at the
simpleVizy
field)1.0.9:
1.0.10:
Steps to reproduce
Craft:dd
the output of Vizy Field 1 and see that it's saved the Vizy Field 2 contents as a string.Additional info
Additional context