Make WordPress Core

Opened 17 years ago

Closed 15 years ago

Last modified 15 years ago

#9772 closed enhancement (duplicate)

in Comments, "In response to" should link to the post, not the post editor

Reported by: thee17 Owned by: janeforshort
Priority: low Milestone:
Component: Comments Version: 2.8
Severity: minor Keywords:
Cc: Focuses:

Description

Change the # on the comments edit page to be more expressive of what it does.

Attachments (2)

9772.diff (1.9 KB ) - added by Denis-de-Bernardy 17 years ago.
9772.patch (1.3 KB ) - added by jakub.tyrcha 15 years ago.

Download all attachments as: .zip

Change History (20)

#1 @markjaquith
17 years ago

What's your suggestion?

#2 @Denis-de-Bernardy
17 years ago

  • Keywords has-patch 2nd-opinion added
  • Milestone 2.92.8
  • Priority normallow
  • Severity normalminor
  • Summary Improve the comment page # symbolin Comments, "In response to" should link to the post, not the post editor

I'd suggest removing it, and replacing the edit link to the post with that of the post's permalink.

It makes a lot more sense: "In response to" should be a link to the post, not to the post editor.

#3 @Denis-de-Bernardy
17 years ago

Jane's input would be useful here.

#4 @Denis-de-Bernardy
17 years ago

  • Keywords tested commit added; 2nd-opinion removed

closed #9350 as dup (with a comment from Jane)

#5 @demetris
17 years ago

This patch is a good fix for that utterly confusing part of the 2.7/2.8 interface.

I approve of it! :-D

#6 @westi
17 years ago

  • Cc janeforshort added
  • Keywords has-patch tested commit removed
  • Milestone 2.82.9
  • Owner set to janeforshort

Punting to 2.9 for Jane to drive a review of the whole page and make it clearer.

Don't tweak, make big improvements.

#7 @Denis-de-Bernardy
17 years ago

  • Type defect (bug)enhancement

#8 @janeforshort
17 years ago

  • Resolutionwontfix
  • Status newclosed

# represents permalink all over the web, which is why it is the link to the live post. The title within the admin is meant to go to the post editor, because that is what post titles do elsewhere in the editor. This change in behavior was intentional.

#9 follow-up: @demetris
17 years ago

  • Resolution wontfix
  • Status closedreopened

The change might have been intentional, but this does not mean it was a good one.

Who uses hash signs to represent permalinks today? Do you use them for this in your blog? Does anyone here use them for this on their blogs? Do they mean anything like this to people using WordPress? (I’m far above average in web-savviness and they mean nothing of the sort to me when I see them there.)

In addition, two of the three links there give no information at all when you hover over them. You have to look at the status bar to see what they are. This is like the web 15 years ago.

In short, this area of the Comments page is a complete disaster.

#10 in reply to: ↑ 9 @Denis-de-Bernardy
17 years ago

Replying to demetris:

Who uses hash signs to represent permalinks today? Do you use them for this in your blog? Does anyone here use them for this on their blogs? Do they mean anything like this to people using WordPress? (I’m far above average in web-savviness and they mean nothing of the sort to me when I see them there.)

+1000 :D

#11 @strider72
17 years ago

+1 from me too. It's a very confusing interface.

Clearly designed by a geek, for a geek. "Regular" people would, I think, assume the "in response to X" link to link the the post to which the comment responds, since that's what it says it links to.

Putting it another way, the comment is not in response to the edit screen.

#12 @ryan
17 years ago

  • Milestone 2.9Future Release

#13 @jakub.tyrcha
15 years ago

Refreshed the patch and cleaned up some code

@jakub.tyrcha
15 years ago

#14 @jane
15 years ago

  • Keywords ux-feedback added

I would be willing to change "#" to "View Post" to be more descriptive (and a bigger link target, which is good for accessibility) but don't want to change the behavior of links on this screen so it is out of sync with every other screen in the admin.

#15 @solarissmoke
15 years ago

  • Keywords ux-feedback removed
  • Resolutionduplicate
  • Status reopenedclosed

This was fixed in #18846 (at least the # issue)

#16 @SergeyBiryukov
15 years ago

  • Milestone Future Release

#17 @jane
15 years ago

Technically should have closed as wontfix, not exactly a dupe.

#18 @solarissmoke
15 years ago

The original ticket description is a dupe - the title was changed half way through and that sort of changed the whole ticket.

Note: See TracTickets for help on using tickets.