Closed ryguy2407 closed 2 years ago
Just as a sanity check I ran all the craft updates locally and pushed to production and I still get the same error when saving any entries that use a vizy field. Any elements that don't have vizy fields save fine.
On my local setup (using Nitro) I can save elements that have vizy fields. Perhaps I should nuke the vendor folder on production and reinstall everything?
Now running Craft 3.7.34
So sorry, I'm such an idiot, I realised that the version I was running was a dev version, I'm not actually sure how that happened, I only run the updates as required but I must've pulled in this version at some stage. After updating to 1.0.9 it all works as expected. Apologies!
Ah, yep sorry about that - still working through some saving issues in craft-3
branch!
I made some changes on my local environment to my vizy field and checked that it was working locally (which is is). I then pushed the changes to production and applied the project config. The changes are applied as expected but when I save an entry with the updated field I get the following error:
Undefined index: type in /var/www/vhosts/newwordorder.com.au/httpdocs/vendor/verbb/vizy/src/helpers/Matrix.php at line 29
I've attached a screenshot of the error as well.
Steps to reproduce
Additional info
Additional context