Display more information for the "Fix validation errors on the related asset." message #9960
-
Craft provides a great feature to prevent an element from saving if related elements have validation errors. However, if there are validation errors in a related element, the error message is pretty technical and doesn't convey enough information to be useful to non-technical folk: "Fix validation errors on the related asset." For example, consider this scenario: We have an asset volume for images with an required field for the image's alt text (used as the We try to use the instructions field to make this more clear, but people don't read … My proposed solution would be to display the specific validation errors of the related asset inline below the generic message above. That would indicate to editors that it's not a bug, but a content-related error that they can fix. Current message
Proposed change
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@brandonkelly @i-just Any update on this? I need more than two hands to count the number of clients who did not get it and required an explanation from us. The current error message is vague, technical, and badly worded.
This is not a good author experience, and also not accessible. We really need better AX here. The message should be clear and actionableFor example:
Might need some adjustments for plurals, different element types etc, but you get the idea. This makes it clear that this is not a misconfiguration that you need to call your developer about, but a content issue that you can fix yourself. What's wrong with the related asset?The error should show a list or summary of validation errors on the related asset(s). Showing a list would be useful:
As an alternative, or maybe if there are a lot of errors, or errors from multiple related assets, it could show a summary instead:
Either of those would make it immediately obvious what the problem is, and how it can be addressed. I realize the second suggestion might be tough to implement. But at least the first suggestion is immediately actionable and would be a great improvement. |
Beta Was this translation helpful? Give feedback.
Agree, that’s a nice improvement.
Went with something similar for Craft 4.16 and 5.8: (adb6229)
Note that we can’t show a nested bullet list, without introducing a breaking change that could also impact front-end templates. Guessing this will give authors enough direction to go on, though.