Make WordPress Core

Opened 17 years ago

Closed 15 years ago

Last modified 13 years ago

#3239 closed defect (bug) (fixed)

User experience for "publishing" private posts should be improved

Reported by: foolswisdom's profile foolswisdom Owned by:
Milestone: 2.5 Priority: normal
Severity: normal Version: 2.0.4
Component: Administration Keywords:
Focuses: Cc:


User experience for "publishing" private posts should be improved

Ticket:3235 describes one problem with the current experience, but it seems that generally that if and how it works should be designed.

Assigning Bryan ticket for major release after the one currently in development.

Change History (6)

#2 @molecularbear
16 years ago

#124 also touches on this subject.

In my opinion, the main problem is that the Publish button overrides the Post Status with no notice or warning of any kind. Even if one assumes that the user knows the difference between Save and Publish, the physical location of the buttons in the UI make it easy to click the wrong one. If the post is published publicly for just a second, RSS readers, spiders, etc can pick it up.

I recognize that most bloggers will probably want to write their content, then click a single button to publish that content publicly. Here are some ideas that might allow us to have our cake and eat it too:

A) Create an option that allows the disabling of the Publish button.

B) Create an option that sets the default action of the Publish button. Right now the default is implicitly, "Save as Public", but one could give the user the ability to change this to "Save as Private".

C) Eliminate the Post Status selection and replace the Save and Publish buttons with: Save Draft, Publish Publicly, Publish Privately - perhaps one could have pretty pictures next to the buttons, i.e. a world globe next to Publish Publicly, a lock next to Publish Privately, etc. Somewhere on the page the current post status could be displayed as an FYI to the user.

#3 @markjaquith
16 years ago

Upon clicking "Publish" we could use JS to check:

  • previous post status
  • currently-desired post status (in Post Status radio)

If either one is "Private," we give them a JS AYS prompt.

#4 @foolswisdom
16 years ago

  • Milestone changed from 2.2 to 2.4

#5 @lloydbudd
15 years ago

  • Owner changed from bryanveloso to anonymous

#6 @thee17
15 years ago

  • Resolution set to fixed
  • Status changed from new to closed

If I'm not mistaken the admin redesign resolves this problem

Note: See TracTickets for help on using tickets.