Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Editablefields don't use drupal field validation for submitted values in views. For example, validation on min / max value.
Comment | File | Size | Author |
---|---|---|---|
#5 | Screen Shot 2016-12-21 at 00.14.15.png | 23.03 KB | johnkareoke |
#5 | Screen Shot 2016-12-21 at 00.14.33.png | 16.68 KB | johnkareoke |
#4 | editablefields-field_validation_2083851-4.patch | 1.19 KB | _vid |
#1 | editablefields-field_validation_2083851-1.patch | 1.19 KB | VasilyKraev |
Comments
Comment #1
VasilyKraev CreditAttribution: VasilyKraev commentedPatch.
Comment #2
dags CreditAttribution: dags commentedVerified the bug and committed the patch to 7.x-1.x. Thanks VasilyKraev.
Comment #4
_vid CreditAttribution: _vid commentedThanks for posting this.
We're still using alpha2 and so updated the patch to work with a clean pull of 7.x-1.0-alpha2. The line numbers on the above patch didn't line up.
Comment #5
johnkareoke CreditAttribution: johnkareoke as a volunteer commentedI am experiencing the same issue - and this patch doesn't seem to resolve it, so despite it being closed, I've posted here. I think this is sufficiently similar to this issue not to open a separate issue. If you disagree, I'm happy to create a new issue.
I have a date field (on an order entity). It has a field validation (rule defined by field_validation module) to ensure it is not in the past. It is validated in the normal display mode (where it is displayed as an editable field), but when it is in a view, validation that the date is not in the past does not occur.
Validation works (Order Expiry field):
Validation (Date not in past) doesn't take place (Order expiry field):
I have applied this patch and it doesn't resolve my issue (either current alpha or dev).
Any pointers in debugging this would be much appreciated.
I have incorrectly posted about this issue in the clientside validation module - but on finding this issue and having tried various ways to debug it, I think it is related to editable fields and views.