You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of our content editors today reported not being able to save an entry. When we looked deeper into it, he had an error on a field or two but in tabs that were hidden by the tab dropdown (he was on a smaller screen). However because he couldn't immediately see where the error occurred he was confused as to why the entry wasn't saving.
What he sees when there is a field error.
Where the errors actually are.
I think adding something to indicate where the error occurs, without having to hunt for it, would offer a benefit. Could be something as small as adding an alert icon to the menu button to show errors exist in the hidden tabs. Maybe something like this?
Even better would be a high contrast list of errors at the top. When you have a lot of fields, or a lot of matrix blocks, it can be hard to find the red outline/text that contains the error. That's a pretty big UX change for errors though.
What do ya'll think?
Steps to reproduce
Create enough tabs so that some are hidden in the tab dropdown.
Add fields to the tabs that are hidden.
Save the entry ensuring a validation error on one of the hidden tabs.
See a pop-up message that the entry couldn't be saved, but nothing more.
Expected behavior
Some kind of visual indication as to where the errors might be located.
Actual behavior
No immediate indication to where the error occurred.
Craft CMS version
4.4.3
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered:
What happened?
Description
One of our content editors today reported not being able to save an entry. When we looked deeper into it, he had an error on a field or two but in tabs that were hidden by the tab dropdown (he was on a smaller screen). However because he couldn't immediately see where the error occurred he was confused as to why the entry wasn't saving.
What he sees when there is a field error.
![Screen Shot 2023-03-23 at 11 41 23 AM](https://user-images.githubusercontent.com/11747187/227263839-67c50d00-c7ac-4aab-9ecf-be652e91c2ed.png)
Where the errors actually are.
![Screenshot 2023-03-23 at 11 48 23 AM](https://user-images.githubusercontent.com/11747187/227263862-1dbb7fed-5e62-49bc-a508-6f771c6667b2.png)
I think adding something to indicate where the error occurs, without having to hunt for it, would offer a benefit. Could be something as small as adding an alert icon to the menu button to show errors exist in the hidden tabs. Maybe something like this?
Even better would be a high contrast list of errors at the top. When you have a lot of fields, or a lot of matrix blocks, it can be hard to find the red outline/text that contains the error. That's a pretty big UX change for errors though.
What do ya'll think?
Steps to reproduce
Expected behavior
Actual behavior
Craft CMS version
4.4.3
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: