Make WordPress Core

Opened 12 years ago

Closed 6 years ago

#17739 closed enhancement (wontfix)

Comment prompt text is misleading

Reported by: jane's profile jane Owned by:
Milestone: Priority: low
Severity: minor Version: 3.2
Component: Text Changes Keywords: has-patch ux-feedback
Focuses: Cc:


The comment form says, "Your email address will not be published."

It can be deceptive b/c people assume it's used for some sort of verification, not that it goes to the site owner/comment moderator, who could very well decide to publish it if he/she happens to be an unethical jerk. People complain about this in support forums and elsewhere every now and then. Quite trivial issue compared to most tickets, but would be nice to take care of it.

Suggestions for better text welcome.

Attachments (2)

17739.diff (6.0 KB) - added by voldemortensen 9 years ago.
17739.2.diff (3.0 KB) - added by voldemortensen 9 years ago.

Download all attachments as: .zip

Change History (28)

#1 @nacin
12 years ago

The text, and "will not be published" as a subset, is pretty much universal on the web, dating to its original appearance in Classic and Kubrick. It's carried over to comment forms of other systems as well.

The word "published" is pretty clear. Also, it's pretty clear that by submitting your email address, it'll go somewhere.

I'm open for a new string, but I definitely can't think of one that isn't too long or too much of a deviation. We went down this path in #13026, because the original string in Twenty Ten was indeed pretty deceptive, and it was opted for the current string to match the historical string.

It's not deceptive as much as people are dumb need education sometimes. :-)

#3 @SergeyBiryukov
12 years ago

#18633 suggested "Your email address will only be visible to the blog owner".

#4 @scribu
12 years ago

"Your email address will only be visible to the blog owner".

That's sounds a lot more accurate. +1

#6 @jane
12 years ago

It "will only be visible to the blog owner" isn't really accurate. Authors, editors, and admins have access also.

Maybe a simple "(Not for display)" or something that doesn't make any action promises, but tries to just communicate intent would be a better path?

#7 @johnbillion
12 years ago

I think "not displayed" is a simple and straight forward enough statement. It doesn't promise that it will "never be published" but it's not overly vague either.

"not displayed with your comment" is another option, but maybe a little too wordy.

#8 @johnbillion
12 years ago

I've just noticed that uses the phrase "not published". This seems like a good, balanced statement.

#9 @Ipstenu
12 years ago

Your email will not be displayed publicly.

Your email will not be displayed with your comment ... I think that's about as good as it's going to get.

Unless we did "Your email will only be visible to blog administrators" (though 'administrators' is the wrong word - managers? Runners? People who run this site and have access to all the wibbly wobbly back end magic.)

#10 @scribu
12 years ago

Wild idea: remove the text completely.

#11 @ryanimel
12 years ago

  • Cc ryan@… added

+1 to removing the text completely. There's no way to tell what the site author/owner will do with email addresses that are submitted, so the site shouldn't make any statement on it.

#12 @JohnONolan
12 years ago

+1 for removing completely. Especially given that if there are other comments on the post, the user can see that no one else's email address has been displayed anyway.

#13 @jameslafferty
12 years ago

Is this something that could be set in Discussion Settings? That way, responsibility for determining appropriate text devolves to the site's administrator. WP could provide an empty string as the default.

#14 @JohnONolan
12 years ago


#15 @jameslafferty
12 years ago

Hear you on that, John, but in this case it seems like removing even the option of setting that text is a bit draconian. That text has been a part of the WP tradition for some time, and its total removal without an easy recourse might be a bit much for some site admins. (I am playing devil's advocate here just a bit... not totally persuaded by my own logic.)

#16 @JohnONolan
12 years ago

I hear you - but don't forget that the comment form can be completely controlled/replaced by the theme so it wouldn't be a huge loss, or hard to add back in. Many themes completely bypass the default form already :)

#17 @jameslafferty
12 years ago

Very good point.

+1 for leaving it out.

#18 @SergeyBiryukov
11 years ago

  • Component changed from UI to Text Changes

9 years ago

#19 @voldemortensen
9 years ago

  • Keywords dev-feedback has-patch added; needs-patch removed

Removed the line from the comment form. Seemed to be the most popular answer

#20 @DrewAPicture
9 years ago

  • Keywords needs-refresh added

@voldemortensen: Looks like some changes to wp-config-sample.php made it into your patch in 17739.diff. Mind regenerating?

#21 @voldemortensen
9 years ago

Removed erroneous file inclusion.

#22 @voldemortensen
9 years ago

  • Keywords needs-refresh removed

#23 @nacin
9 years ago

  • Keywords ux-feedback added; dev-feedback removed

My opinion remains unchanged: the text should stay exactly as is.

I'd be up for discussing this at a dev meeting and seeing what others think.

I also kind of want to reach out to some indie web and privacy folks and see if they have an opinion on it.

#24 @chriscct7
8 years ago

  • Priority changed from lowest to low
  • Severity changed from trivial to minor

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

6 years ago

#26 @karmatosed
6 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

We discussed this ticket in this week's design triage session. It's been a while without any action on this. We are agreeing to close for now. If someone feels passionately about it, we can reconsider - we would be keen to have evidence of this as an issue when we do that.

Note: See TracTickets for help on using tickets.