Closed (outdated)
Project:
Webform Validation
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Dec 2018 at 13:48 UTC
Updated:
17 Apr 2026 at 20:37 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
civifirst john commentedAdded a change to the value comparison operator. Considered adding "equals" to the operator, but didn't as it's a separate option already.
Comment #3
civifirst john commentedPatch added
Comment #4
liam morlandHow about implementing this by making the "Equal values" validator accept the negate option?
Comment #5
3liNeeded the ability to negate equals value, patch attach does this.
Comment #6
liam morlandThanks for the patch. Patches need to be made from the module directory. This means that they do not include "sites/all/modules" etc. They also need to be made with unix-style line endings. Otherwise, they won't apply and be tested by the automated testing. Attached is a re-roll of the patch.
This works for ensuring that two components have different values. For three or more, it only checks that they later components are different from the first, not that they are all different from each other, which I think is what is implied by this validator.
Comment #7
liam morlandComment #8
ayduns commentedDoesn't the existing 'Unique values' rule cover this case? Add a 'Unique values' rule and choose the first and last name fields.
Comment #9
liam morlandDrupal 7 is no longer supported. If this applies to a supported version, please re-open.