Make WordPress Core

Opened 12 years ago

Closed 10 years ago

#22961 closed enhancement (fixed)

"Allow link notifications from other blogs (pingbacks and trackbacks.)" description is misleading

Reported by: mark-k's profile mark-k Owned by: chriscct7's profile chriscct7
Milestone: 4.3 Priority: normal
Severity: normal Version:
Component: Text Changes Keywords: has-patch
Focuses: ui, administration Cc:

Description

The description for enabling pingbacks and trackback is "Allow link notifications from other blogs (pingbacks and trackbacks.)". Which is not correct a more appropriate description should be "By default new posts can recieve notification (pingbacks and trackbacks) from other blogs".

The current description is broken in particular when the option is not set which leads to the assumption that the pingbacks and trackbacks are block while they are not as they are still enabled for posts which were create before the option was disabled.

Attachments (1)

22961.patch (1.5 KB) - added by chriscct7 10 years ago.

Download all attachments as: .zip

Change History (15)

#1 @ocean90
12 years ago

  • Component changed from Comments to Text Changes

#2 @DrewAPicture
12 years ago

  • Keywords ux-feedback added

#3 @mark-k
12 years ago

Ok, maybe it was just me focusing on the right hand side and ignoring the "Default article settings" on the left:( but I still think it is confusing. The style in the line below it - "Allow people to post comments on new articles" is better IMO.

#5 @chriscct7
10 years ago

  • Focuses ui administration added
  • Keywords has-patch added; ux-feedback removed
  • Type changed from defect (bug) to enhancement

The toggle for comments reads "Allow people to post comments on new articles" which shows the clear distinction in that the setting only affects new posts. I kind of agree this change makes it more clear what the setting really does. Patch changes the text from "Allow link notifications from other blogs (pingbacks and trackbacks)" to "Allow link notifications from other blogs (pingbacks and trackbacks) on new articles" for both the XML RPC settings and the WordPress Discussion settings consistent with the wording for the comments settings

@chriscct7
10 years ago

#6 @chriscct7
10 years ago

  • Milestone changed from Awaiting Review to 4.3
  • Owner set to chriscct7
  • Status changed from new to accepted

#7 @chriscct7
10 years ago

  • Keywords commit added

#8 follow-up: @obenland
10 years ago

  • Keywords commit removed

Do we use the word "article" over "post", @helen?

#9 in reply to: ↑ 8 @chriscct7
10 years ago

Replying to obenland:

Do we use the word "article" over "post", @helen?

It's called "article" for consistency with the setting directly above it "Attempt to notify any blogs linked to from the article" and the one right below it "Allow people to post comments on new articles", and the description under that "(These settings may be overridden for individual articles.)". The section it is in is even called "Default article settings", and there is another setting on the same page called " Automatically close comments on articles older than".

I think there was a deliberate attempt to avoid using the word "post" as in "a single post" as "post" is used as a verb twice on that page which could make it confusing

#10 @chriscct7
10 years ago

This might make the usage in context clearer: http://screencloud.net/v/Gz5

#11 @chriscct7
10 years ago

If we're going to switch them all to post, I think that should be done in a separate ticket as there's going to need to be a discussion about:

  1. Rephrasing other settings to stop using "post" as a verb and more importantly
  2. Since these settings are for comments, and you can have comments on a non post, like in a page or custom post type, whether that's more confusing to users to use "post" than it already is. For example, if we switch them to post, users might be confused over where the comment settings are for pages.

That type of text change would probably need to be thought out, and I would think the UX team would want to do a new user experience A/B test on that to ensure it's not more confusing.

#12 follow-up: @obenland
10 years ago

That's fine, I was just wondering. The context makes sense.

#13 in reply to: ↑ 12 @chriscct7
10 years ago

Replying to obenland:

That's fine, I was just wondering. The context makes sense.

Yep, not a problem. I probably should have explained that better on the ticket. Did you want to re-add commit or still have @helen swing on by before that?

Last edited 10 years ago by chriscct7 (previous) (diff)

#14 @obenland
10 years ago

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

In 32569:

Improve description for link notification option.

Makes it clear that the option only applies to new articles.

Props chriscct7.
Fixes #22961.

Note: See TracTickets for help on using tickets.