Changes between Initial Version and Version 6 of Ticket #29087
- Timestamp:
- Aug 30, 2019, 2:30:55 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29087
- Property Triage Stage Unreviewed → Accepted
- Property Owner set to
- Property Status new → assigned
- Property Has patch set
-
Ticket #29087 – Description
initial v6 38 38 3. Click '''SAVE'''. There will be a validation error, as expected, because last_name is not provided. However, the '''Delete''' button is missing: [[Image(https://s13.postimg.org/3q0hrduyf/image.png)]] 39 39 4. '''The user is now forced to either (a) fix the validation error or (b) reload the page, discarding all unrelated changes on the page. It is not possible for the user to fix the validation error by simply canceling/deleting the pending new record.''' 40 41 42 43 ---- 44 45 ==== It is actually worse than that... 46 47 Another cause of validation errors can be uniqueness constraints. These errors can be difficult to fix and sometimes actually cannot be fixed. So it is totally possible that because of a validation error the user is **forced to reload the page**, there is no other choice. 48 49 Building on the models above, here is an example of a validation error that can be unsalvageable for users without the `create` permission for groups. New `Council` model is added, a foreign key from `Person` to `Council` is created and also a constraint with `unique_together = ('council', 'group')` is set. 50 51 [[Image(https://i.ibb.co/41gpvgS/Screenshot-2019-08-30-at-21-08-13.png)]]