Opened 9 years ago
Closed 5 years ago
#1453 closed defect (bug) (fixed)
Better error message when non-logged in users view the newticket page
Reported by: | johnbillion | Owned by: | dd32 |
---|---|---|---|
Milestone: | Priority: | high | |
Component: | Trac | Keywords: | has-ui-feedback |
Cc: |
Description
When linking a user to https://core.trac.wordpress.org/newticket, they see a nasty error message if they're not logged in. Can we make this error a bit more user-friendly?
Attachments (4)
Change History (14)
This ticket was mentioned in Slack in #meta-tracdev by drew. View the logs.
9 years ago
#5
in reply to:
↑ 4
@
7 years ago
Replying to Mte90:
The message is different now so this ticket is required?
The form is there if you're already logged in.
If you're not logged in yet, there's still the same error message, exactly as reported.
#6
@
7 years ago
I like the suggestion from @JoshuaWold. Just the Font-size from the close button should be a bit larger, cause its pretty small and hard to read. Also do change the design of the button, could be useful, cause the color contrast of the border ist not really high.
#7
@
7 years ago
- Keywords has-ui-feedback added; ui-feedback removed
How about the styling remains the same and the text is simple: "You need to login to create a new ticket."
This ticket was mentioned in Slack in #design by karmatosed. View the logs.
6 years ago
#9
@
6 years ago
iIt looks like this was somewhat improved over the years by linking to
https://login.wordpress.org/?redirect_to=https://core.trac.wordpress.org/newticket
instead of just https://core.trac.wordpress.org/newticket
(relevant commits: [341], [361], [3139]), so that you only see the form once you're logged in, instead of the error message.
It would be great to improve the original message and get rid of the redirect_to
workaround, but the message appears to be in Trac's perm.py
file, and I'm not sure if there's an easy way to customize it.
@samuelsidler what kind of flexibility is there in updating the error? I'm guessing we mostly have control over the wording of the error, and not the overall layout. The first thought I had was to clean it up by removing the red error part, and rewording the H1 error message. Thoughts?