-
Notifications
You must be signed in to change notification settings - Fork 14
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
"Could not save field." #26
Comments
@havardlj - it should not be failing silently. The new custom validator only fires on three specific cases.
You can take a look here CalendarizeValidator.php Could you share what your calendarize field looks like? |
It fails before getting to any of those steps |
I ran into this as well. This is the place where it fails: https://github.com/craftcms/cms/blob/master/src/services/Fields.php#L755 When I commented the I do not know much about these validators and I can't seem to figure out which specific validator fails, but maybe it helps to know it's the validator anyway. |
Just pushed a fix for this. The validation rules were in the incorrect place. I am currently working on adding better unit testing to this plugin to avoid these issues in the future. |
Getting "Could not save field." without any error message under any inputs when creating/editing existing calendarize-fields after latest plugin update. Can't find anything in the error logs either.
The text was updated successfully, but these errors were encountered: