Make WordPress Core

Opened 9 years ago

Closed 8 years ago

Last modified 8 years ago

#9910 closed enhancement (wontfix)

"Update page" is totally unclear

Reported by: novalis_dmt Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.8
Component: UI Keywords:
Focuses: Cc:


On the edit page page, at http://example.com/wp-admin/page.php?action=edit&post=200 there is a button called "Update page". It should say something like "save page", since update could mean "update this page (that is, the edit page) to the latest saved version from Bob (who is editing at the same time as you).

Change History (9)

#1 @dd32
9 years ago

Doesn't the WordPress Edit lock prevent 2 people making updates to a page/post?

#2 @Denis-de-Bernardy
9 years ago

  • Milestone changed from Unassigned to 2.8

#3 @Denis-de-Bernardy
9 years ago

  • Milestone changed from 2.8 to Future Release

punting pending patch

#4 @Denis-de-Bernardy
9 years ago

  • Component changed from Administration to UI

#5 @Denis-de-Bernardy
9 years ago

  • Keywords needs-patch added
  • Type changed from defect (bug) to enhancement

#6 @mrmist
8 years ago

  • Keywords needs-patch removed
  • Resolution set to worksforme
  • Status changed from new to closed

I think that the wording is clear enough, and as dd32 said I don't think that the multiple edit scenerio should be possible at any rate.

Also if you changed the wording to "save page" or whatever, someone could think of a reason why that is unclear, too.

#7 @jane
8 years ago

  • Resolution worksforme deleted
  • Status changed from closed to reopened

@dd32: The edit lock pops a big red warning that someone else is editing, and stays on longer than there are really 2 people trying to edit. (We should make that flow better in future.)

The text changes to Update Page because it is, in fact, updating the published page, not just saving a new draft that you can publish at a later time. Your request is really asking for a change to the flow of the application, not just a button change. Closing as won't fix. If someone wants to propose a new feature that actually branches a piece of content to allow for this type of multi-threaded saving (would be a nice feature, but maybe plugin territory for now), it should be on a new ticket as a feature request.

Reopening so I can close as wontfix rather than worksforme.

#8 @jane
8 years ago

  • Resolution set to wontfix
  • Status changed from reopened to closed

#9 @nacin
8 years ago

  • Milestone Future Release deleted
Note: See TracTickets for help on using tickets.