-
Notifications
You must be signed in to change notification settings - Fork 73
Incomplete, previously valid content bypasses new validation rules #395
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
Comments
Thanks for the heads-up. Will check what’s happening. |
@toondkn Can you provide the (partial) config to reproduce the issue? |
I cannot reproduce the issue locally; the validation works as expected for a duplicate entry. It may be related to a specific field configuration, or perhaps your site config is cached. |
Thanks for checking. I tried reproducing with a minimal example, and it indeed works as expected, great! I will try to replicate the behavior with the exact collection config and report back. |
Managed to reproduce the issue with the following collection config and piece of content. The exact collection config entry, for completeness' sake:
This is an existing incomplete entry, that when duplicated, can be saved while some required fields are not filled in:
Note that the widget for field with name |
Thanks! Will check back later today. |
I can confirm the issue, which actually happens even without duplicating an entry. I’ll overhaul the validation code to fix the problem. |
Sorry to keep you waiting 🙇🏼 I realized that the current entry validator isn’t quite right. So I have to rewrite the whole validator code with automated tests written. I plan to finish it in a few weeks. |
Hey no pressure! Thanks for building this great project. |
Steps to reproduce:
This opens a gap where bad data can easily enter the system, causing confusion for cms users and extra work for implementers.
The text was updated successfully, but these errors were encountered: