WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 13 months ago

#18418 closed enhancement (fixed)

Clarifying what "Private" means in post visibility

Reported by: danielbachhuber Owned by: wonderboymusic
Milestone: 4.4 Priority: normal
Severity: normal 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 (4)

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

Download all attachments as: .zip

Change History (26)

#1 @danielbachhuber
5 years ago

  • Type changed from defect (bug) to enhancement

@danielbachhuber
5 years ago

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

#2 @PeteMall
5 years ago

  • Milestone changed from Awaiting Review to 3.3

#3 @danielbachhuber
5 years ago

  • Keywords has-patch added

#4 @SergeyBiryukov
5 years ago

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

#5 @danielbachhuber
5 years ago

That makes sense to me too

#6 @westi
5 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.

#7 @jane
5 years ago

  • Component changed from General to UI

Agree with westi. I don't want that long of a string cluttering up things. Also @danilbachhuber, 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.

Version 0, edited 5 years ago by jane (next)

#8 @ryan
5 years ago

  • Milestone changed from 3.3 to Future Release

Punting enhancements from 3.3.

#9 @sabreuse
4 years ago

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

#10 follow-up: @sillybean
3 years 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.

#11 in reply to: ↑ 10 @helen
3 years 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.

@sillybean
3 years ago

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

@sillybean
3 years ago

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

#12 @sillybean
3 years 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.

#13 @chriscct7
13 months ago

  • Keywords needs-refresh added
  • Milestone changed from Future Release to 4.4
  • Owner changed from danielbachhuber to chriscct7
  • Severity changed from minor to normal
  • Status changed from new to assigned

#14 @wonderboymusic
13 months ago

  • Owner changed from chriscct7 to wonderboymusic

18418.diff is a refresh

#15 @wonderboymusic
13 months ago

  • Keywords needs-refresh removed

#16 @wonderboymusic
13 months ago

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

In 34004:

Cleanup the text for Publish Settings > Publish in the edit-form-advanced help tab. Clarify that Private posts aren't hidden from editors and administrators.

Props sillybean.
Fixes #18418.

#17 @ryan
13 months ago

  • Keywords needs-screenshots added

I'm going to add some before and after screenshots. I'm attempting before and after shots of all visual changes on multiple devices. Screenshots are used in visual changelogs and the Today in the Nightly posts, all of which increases awareness of our usability and make ui review easier. https://make.wordpress.org/core/tag/today-in-the-nightly/

If you'd like to help collect visuals, we want before and after screenshots on at least two devices, with one of them preferably being a phone. We're increasing our mobile/touch awareness by testing and capturing all visual changes from phones. Provide whatever screenshots you can. The Flow Patrol team will handle the remainder. Developers, taking screenshots of your patches and commits really helps ui/ux review and flow patrol. https://make.wordpress.org/flow/

Last edited 13 months ago by ryan (previous) (diff)

#18 follow-up: @pavelevap
13 months ago

Why was this help paragraph splitted into several strings? It is one long text and for translators is better when they translate it at once? There was no visual change and splitting strings is not helpfull...

#19 in reply to: ↑ 18 @ryan
13 months ago

Replying to pavelevap:

Why was this help paragraph splitted into several strings? It is one long text and for translators is better when they translate it at once? There was no visual change and splitting strings is not helpfull...

Indeed. This adds concatenation and reduces context, things we avoid when marking strings. Suggest revert.

#20 @ryan
13 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

#21 @ryan
13 months ago

  • Keywords needs-screenshots removed

#22 @wonderboymusic
13 months ago

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

In 34016:

After [34004], don't break apart the paragraph into multiple translatable strings.

Fixes #18418.

Note: See TracTickets for help on using tickets.