Opened 13 years ago
Closed 7 years ago
#3330 closed enhancement (maybelater)
Improving the error messages UI
Reported by: | xeqta | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Core | Keywords: | trac-tidy-2018 |
Cc: |
Description
Not sure if this has been discussed before or if there's already an enhancement ticket in trac?
I suggest we improve the UI of these kind of error-messages:
- "Please enter some content to post" (When you forget to type something in the textfield)
- "There was an error sending that message, please try again" (In Messages)
- Ect.
Suggestions:
- When there's an error, the message should always be either a drop-down-bar from the absolute top of the site or a simple div-popup in the middle of the site. That way the error-messages won't throw around with other design elements (like pushing down other elements) in order to make room for the error-message. This does not look or feel good.
- If choosing the div-pop you can click outside it to make it go away or click a "dismiss" link.
- If choosing the drop-down-bar, the bar will slide down and you will have to click the "dismiss" link or correct your error on the site in order to make it disappear. The bar should be colored (eventually light yellow or red) in order to gain user attention.
Other notes:
- It will be easier to style the site from the included template since you don't have to worry about error messages that push around other elements. The error messages will always be shown in a consistent location and consistency is always good.
Change History (4)
#1
@
13 years ago
- Milestone changed from Awaiting Review to Future Release
#2
@
10 years ago
- Severity set to normal
Standardizing this treatment, and in particular moving away from the current (crummy) 'template_notices' implementation, is a worthwhile project. If any intrepid designers want to have a go at mocking it up, please feel free to take the reins.
#3
@
7 years ago
- Keywords trac-tidy-2018 added
We're closing this ticket because it has not received any contribution or comments for at least two years. We have decided that it is better to close tickets that are good ideas, which have not gotten (or are unlikely to get) contributions, rather than keep things open indefinitely. This will help us share a more realistic roadmap for BuddyPress with you.
Everyone very much appreciates the time and effort that you spent sharing your idea with us. On behalf of the entire BuddyPress team, thank you.
If you feel strongly that this enhancement should still be added to BuddyPress, and you are able to contribute effort towards it, we encourage you to re-open the ticket, or start a discussion about it in our Slack channel. Please consider that time has proven that good ideas without contributions do not get built.
For more information, see https://bpdevel.wordpress.com/2018/01/21/our-awaiting-contributions-milestone-contains/
or find us on Slack, in the #buddypress channel: https://make.wordpress.org/chat/
I want to look at the way notifications, in general, are dealt with (though it may end up being a theme-specific issue), so thanks for your ideas.