Actions
Bug #7795
closed
Ajax validation caching causing odd validation behavior
Description
Due to the validation caching and always validating as true if previous value is same as new value there can be cases where the existing value doesn't pass validation and returns true when it should invalidate.
Updated by krileon almost 5 years ago
This is due to allowing additional fields in the validation. Those fields also need to be considered in the cache.
Updated by krileon almost 5 years ago
Previous value caching shouldn't even exist for code validation. Completely remove that caching and issue resolves. We always want to evaluate the code validation. Same change is needed for query validation as well.
Updated by krileon almost 5 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Actions