-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't remove entries in an Entries field within a Vizy block #299
Comments
This would have to do with our mitigation of field changes until you interact with the field. This is done so that content changes aren't triggered when you haven't changed anything in the field. This is most common for nested Vizy fields, but can happen on just single level ones. We watch for when you click in on a Vizy field, and have a flag to stop any changes from being recorded. Bizarrely, this doesn't seem to be triggered when clicking the remove button on an element select. Everything else about clicking in on a Vizy field and Vizy block is working correctly, but not the remove button. You can confirm this by clicking on anything else in the field first, then removing the entries. Looking into options... |
Fixed for the next release. To get this early, run |
Fixed in 2.1.20 |
@engram-design this is still an issue (or maybe is back?) on Vizy 3.0.4 - Craft 5.4.7.1 |
Fixed for the next release. To get this early, run |
Fixed in 3.0.5 |
Describe the bug
I feel like this is a new bug because I would have noticed it before, but if you create a simple Vizy block with just an Entries field, you can add to it fine but can't remove entries. If you save and go back to the post, the entries you've deleted are still there.
If you remove all of them it seems to work.
Opening the entry
Removing one related entry, before saving
After saving and re-opening, it's still there
Thank you!
Steps to reproduce
Craft CMS version
4.8.10
Plugin version
2.1.19
Multi-site?
No
Additional context
No response
The text was updated successfully, but these errors were encountered: