WordPress.org

Make WordPress Core

Opened 3 years ago

Last modified 9 months ago

#18418 new enhancement

Clarifying what "Private" means in post visibility

Reported by: danielbachhuber Owned by: danielbachhuber
Milestone: Future Release Priority: normal
Severity: minor Version:
Component: Text Changes Keywords: has-patch
Focuses: ui Cc:

Description

When choosing visibility for a single post, “Private” doesn’t make much sense as a label and requires extra explanation as to whom the post will be private to.

Context: At the Newbie Workshop during WCSF 2011, we had to talk brand new users through the myriad of features offered in WordPress. "Private" as a post visibility required extra explanation and even I realized I didn't know what it did.

"Private" should be replaced with text like "Private to blog editors and administrators"

Attachments (3)

privatetext.18418.1.patch (2.6 KB) - added by danielbachhuber 3 years ago.
Replace "Private" text with "Private to blog editors and administrators"
private-status-help.diff (2.3 KB) - added by sillybean 9 months ago.
Adding to the help text on publish settings to clarify what "private" does
private-status-help2.diff (2.3 KB) - added by sillybean 9 months ago.
Help text to clarify what "private" and "password protected" mean

Download all attachments as: .zip

Change History (15)

comment:1 danielbachhuber3 years ago

  • Type changed from defect (bug) to enhancement

danielbachhuber3 years ago

Replace "Private" text with "Private to blog editors and administrators"

comment:2 PeteMall3 years ago

  • Milestone changed from Awaiting Review to 3.3

comment:3 danielbachhuber3 years ago

  • Keywords has-patch added

comment:4 SergeyBiryukov3 years ago

Maybe just “Private to editors and administrators”, without “blog”?

comment:5 danielbachhuber3 years ago

That makes sense to me too

comment:6 westi3 years ago

I'm not sure that adding this longer string actually improves this much.

Private posts are confusing in general and we don't support them very well - I think we need to step back and decide whether or not we want to keep them at all and how they should be presented from a UX perspective.

comment:7 jane3 years ago

  • Component changed from General to UI

Agree with westi. I don't want that long of a string cluttering up things. Also @danielbachhuber, you were doing the newbie workshop using wordpress.com, which has an entirely additional level of confusion because of the existence of private blogs there. I would rather .org support a fully private blog than individual private posts, as realistically you could just save posts as draft in a lot of the use cases for that feature.

Last edited 3 years ago by jane (previous) (diff)

comment:8 ryan3 years ago

  • Milestone changed from 3.3 to Future Release

Punting enhancements from 3.3.

comment:9 sabreuse15 months ago

  • Component changed from UI to Text Changes
  • Keywords ui-focus added; ux-feedback removed

comment:10 follow-up: sillybean9 months ago

I agree that adding a long string doesn't help the situation -- especially given that plugins can change the privacy-related roles.

Maybe fixing #7745 would help this situation as well.

comment:11 in reply to: ↑ 10 helen9 months ago

Replying to sillybean:

especially given that plugins can change the privacy-related roles.

Yep. Maybe something about what it does (by default) would be good in the help tab - I didn't see it on a quick glance.

sillybean9 months ago

Adding to the help text on publish settings to clarify what "private" does

sillybean9 months ago

Help text to clarify what "private" and "password protected" mean

comment:12 sillybean9 months ago

Updated the patch to break up the Publish section into separate strings for each topic. I've left the Format and Thumbnail sections alone because their text is more cohesive.

Note: See TracTickets for help on using tickets.