Closed d-karstens closed 2 months ago
Now this is going to be tricky, and we've known about this for a little bit. But basically, Matrix fields' new behaviour is that it relies on a parent element for a lot of things. In a normal scenario, this would be the owner entry, or a parent Matrix block. But as this is connected with a Vizy block, which isn't an element (and isn't saved as one due to performance), this makes it impossible to use Matrix fields and other element-like fields (addresses) with Vizy.
We're obviously looking for solutions to this!
Should be fixed for the next release. To get this early, run composer require verbb/vizy:"dev-craft-5 as 3.0.0-beta.4"
.
Thanks! Matrix fields appear to be working now, but have encountered another issue when trying to save Vizy blocks containing Hyper fields - posting here as it seems to have started happening after applying that update (confirmed this by downgrading and testing again)
Let me know if you need more details
Should be fixed (again) for the next release. To get this early, run composer require verbb/vizy:"dev-craft-5 as 3.0.0-beta.4"
.
Fixed in 3.0.0-beta.5
hi! for me matrix field also don't work, I get the following error when trying to add a block:
"Invalid owner ID: 506189594"
the response:
using: craft 5.2.2 vizy 3.0.0-beta.5
Can you let me know what "View Mode" the Matrix field is set to? Vizy only supports "As inline-editable blocks".
Describe the bug
Hi,
After upgrading to Craft 5 we've encountered this issue with Vizy blocks containing matrix field
When trying to add a block to content we get the following message![Screenshot 2024-03-28 at 11 21 00 am](https://github.com/verbb/vizy/assets/21274925/2eb0ae2f-9d14-444c-89e0-f0dbb467324d)
And this error happens when trying to save the entry, or when trying to access an old entry that had the block before migrating![Screenshot 2024-03-28 at 11 19 53 am](https://github.com/verbb/vizy/assets/21274925/b418c1fa-a53c-46da-a721-7fb80f7d88f8)
Steps to reproduce
Craft CMS version
5.0.0
Plugin version
3.0.0-beta.4
Multi-site?
No
Additional context
No response