WordPress.org

Make WordPress Core

Opened 9 years ago

Last modified 6 months ago

#17028 new enhancement

Move the "last edited at" text and saved/updated/published notices in post/page editor

Reported by: jane Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.1
Component: Editor Keywords: editorial-flow has-patch needs-testing ux-feedback needs-refresh close
Focuses: ui, administration Cc:
PR Number:

Description

  1. The timestamp of the last save is currently displayed at the bottom right of the editor box. It would make more sense for this information to be tied to the Publish box instead.
  1. The yellow alert boxes that appear at the top of the page are weird. a) They should appear closer to the button that caused the action (general usability/accessibility best practice), so probably by the Publish box. b) Once you edit anything on the screen, the "post updated" (or saved, etc) text should go away, because it is no longer current.

Am thinking we could combine these two things into one flexible status message that's located in or adjacent to the Publish box.

Attachments (2)

patch.diff (2.4 KB) - added by trewelu 7 years ago.
17028.patch (1.0 KB) - added by rhyswynne 5 years ago.
patch.diff produced a notice error. Fixed by using $post->ID rather than $post_ID. Probably needs some UI work.

Download all attachments as: .zip

Change History (15)

#1 @scribu
8 years ago

Related: #17906

#2 @danielbachhuber
7 years ago

  • Keywords editorial-flow added

#3 @DrewAPicture
7 years ago

  • Component changed from UI to Administration
  • Keywords ui-focus added

#4 @nacin
7 years ago

  • Milestone changed from Awaiting Review to 3.6

@trewelu
7 years ago

#5 @trewelu
7 years ago

  • Keywords has-patch needs-testing added; needs-patch removed

#6 @DrewAPicture
7 years ago

  • Milestone changed from 3.6 to Future Release

#7 @ocean90
6 years ago

  • Component changed from Administration to Editor

@rhyswynne
5 years ago

patch.diff produced a notice error. Fixed by using $post->ID rather than $post_ID. Probably needs some UI work.

#8 @chriscct7
4 years ago

  • Focuses administration added
  • Keywords ux-feedback needs-refresh added
  • Priority changed from low to normal

This ticket was mentioned in Slack in #core-editor by iseulde. View the logs.


4 years ago

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


2 years ago

#11 @melchoyce
2 years ago

6 years old, but still very relevant — and things to keep in mind for Gutenberg. :)

I imagine at this point those patches are out of date. Points 1 and 2a could use some UI design. 2b should probably be a separate ticket at this point.

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


17 months ago

#13 @garusky
17 months ago

  • Keywords close added

A few weeks ago we discussed in the design channel on this old ticket. We agreed that adjusting the classic editor at this point is something we can avoid and focus on Gutenberg.
However, I wanted to analyze better the point 2 and on the user experience side I would like to add that:

  1. Moving the notification messages near the publish box would be negative on mobile because when the page is reloaded, the page itself scroll to the top and they will not be seen anymore.
  2. Some texts of the notifications are very long (for example that of the revisions) and they would be difficult to lay out in the small publish box.

For these reasons I suggest closing this task for points 1. and 2a.

As suggested by @melchoyce I opened a separate ticket #44626 for point 2b.

Note: See TracTickets for help on using tickets.