WordPress.org

Make WordPress Core

Opened 9 years ago

Closed 8 years ago

#16061 closed enhancement (fixed)

You are not allowed to edit comments on this post.

Reported by: waclawjacek Owned by:
Milestone: 3.1 Priority: normal
Severity: trivial Version: 3.1
Component: I18N Keywords: 3.2-early has-patch
Focuses: Cc:

Description

"You are not allowed to edit comments on this post, so you cannot edit this comment." (pot/trunk/wordpress.pot)

I think it's pretty self-explanatory that if I can't edit comments on a post, I can't edit a comment on that post. I guess "You are not allowed to edit comments on this post" would be better.

Wdyt? :-)

Best regards,
WJ

Attachments (1)

16061.diff (2.4 KB) - added by mikeschroder 9 years ago.
Initial patch -- "You do not have sufficient permissions to edit ..."

Download all attachments as: .zip

Change History (7)

#1 @jane
9 years ago

"Not allowed" sounds like a child being scolded. We should probalby change to something like, "You do not have sufficient permissions to edit comments." or "You do not have sufficient permissions to edit this comment."

#2 @dd32
9 years ago

"You do not have sufficient permissions to edit comments on this post" fits the logic and english standards better IMO.

#4 @westi
9 years ago

  • Keywords 3.2-early added
  • Milestone changed from Awaiting Review to Future Release
  • Summary changed from "You are not allowed to edit comments on this post, so you cannot edit this comment." to You are not allowed to edit comments on this post.

Updated title to match change already made.

We should do better in 3.2

@mikeschroder
9 years ago

Initial patch -- "You do not have sufficient permissions to edit ..."

#5 @mikeschroder
9 years ago

  • Cc mike.schroder@… added
  • Keywords has-patch added

Uploaded initial patch to make this change, but I'll note that the "You are not allowed" is a lot more prevalent than *just* for editing comments.

Is this something that should really be changed for all the error messages that mention "You are not allowed"?

#6 @ryan
8 years ago

  • Milestone changed from Future Release to 3.1
  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [17232]

Note: See TracTickets for help on using tickets.