Closed bleepsandblops closed 2 months ago
Looks related to https://github.com/verbb/vizy/issues/282 but there are no nested Vizy fields here
I can't replicate this with your exact setup I'm afraid. Does saving the entry and re-loading change the behaviour at all?
No it doesn't...
Did some more testing, I have another Vizy field with lots of blocks too, and this one doesn't exhibit that behaviour unless I add a block with a sub Vizy field (so clear case of https://github.com/verbb/vizy/issues/282).
But for the one in my screenshot, I can't really make sense of it as not even the available blocks have sub Vizy fields.
Did some more digging, if I open the entry, I immediately get that message, then if I look in the network tab I can see a call to the admin/actions/elements/save-draft
action with those two lines in the payload:
fields[contentPage][vizyData]: [{"type":"vizyBlock","attrs":{"id":"vizy-block-ZymZBfJ4v0","enabled":false,"collapsed":true,"values":{"type":"type-vZc30jrmgy","content":{}}}},{"type":"vizyBlock","attrs":{"id":"vizy-block-VLavpzygWv","enabled":false,"collapsed":true,"values":{"type":"type-elc8vQ9oNw","content":{}}}}]
modifiedDeltaNames[]: fields[contentPage]
If I save and open again, exact same content for those two lines. And if I open the content
table I can also see for that field the exact same json...
So I don't understand what it thinks has changed? Anything else I can look at?
Fixed for the next release. To get this early, run composer require verbb/vizy:"dev-craft-4 as 2.1.18"
.
Fixed in 2.1.19
Describe the bug
If I have a Vizy field with one block (or more) in it, the CP shows the message "Showing your unsaved changes" on opening the entry, before doing anything in it, not even focusing in the Vizy field. It shows the Vizy field with the blue border indicating that that's the field that has changed.
Cf screenshot below, I've even tried with a field that's just an UI element so literally nothing to change in it.
Steps to reproduce
Craft CMS version
4.8.1
Plugin version
2.1.16
Multi-site?
No
Additional context
This doesn't happen if the field is left completely empty.