You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to add Matrix blocks to a Vizy field, both Blocks only and Rich text and Blocks in Craft 5.
It is currently possible to set it up in a Vizy field, but when trying to add it on an Entry it returns Invalid owner ID error message.
What's your proposed solution?
I currently have no proposed solutions for this.
But either make it possible, or remove the option to add Matrix fields to a Vizy field to make it more clear to the user.
Additional context
As talked about on Discord.
The text was updated successfully, but these errors were encountered:
There are some complications unfortunately to using Matrix within Vizy fields in Craft 5. This is because unlike Craft 4, Matrix in Craft 5 is all about entries. Matrix fields require the "owner" (in this case, a Vizy field) to be a saved element, but for performance gains, we don't use elements for Vizy.
We've made some workarounds for "As inline-editable block" mode for Matrix fields, and that should be working. Any of the other layouts unfortunately have a different implementation don't currently work.
We're actively looking into a solution for this though, particularly seeing how things like CKEditor deals with this same issue, and working with the Craft team about it.
What are you trying to do?
I would like to be able to add Matrix blocks to a Vizy field, both Blocks only and Rich text and Blocks in Craft 5.
It is currently possible to set it up in a Vizy field, but when trying to add it on an Entry it returns Invalid owner ID error message.
What's your proposed solution?
I currently have no proposed solutions for this.
But either make it possible, or remove the option to add Matrix fields to a Vizy field to make it more clear to the user.
Additional context
As talked about on Discord.
The text was updated successfully, but these errors were encountered: