[wp-trac] [WordPress Trac] #14530: "Cheatin', uh?" is not helpful feedback for users or developers

WordPress Trac noreply at wordpress.org
Wed Sep 2 22:43:43 UTC 2015


#14530: "Cheatin', uh?" is not helpful feedback for users or developers
-------------------------------------+-----------------------
 Reporter:  shidouhikari             |       Owner:
     Type:  enhancement              |      Status:  reopened
 Priority:  normal                   |   Milestone:  4.4
Component:  Role/Capability          |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  ui
-------------------------------------+-----------------------

Comment (by kraftbj):

 Replying to [comment:74 juliobox]:
 > Hello
 >
 > I'm wondering why do we had so many strings to translate and why do we
 explain more each security message.
 > Yes i talk about security messages because if someone reach a "Cheatin
 uh" message, this is because he hacked something to try to do something he
 couldn't, following me?
 >

 While rare, there are legit situations where "Cheatin" revealed itself.
 Example in this testing steps here:
 https://core.trac.wordpress.org/ticket/33684#comment:1

 > So, look at this one #21076, we deprecated the function
 ''wp_explain_nonce'' because it was not secure to add a too specific
 message, '''and''' also there were too many strings to translate for not
 so usefull feature.
 >

 For the breakout patches, I tried to reuse strings as much as possible and
 keep them semi-useful, semi-vague. The idea is to have more specific
 messaging returned when `WP_DEBUG` is enabled to help developers if they
 built something that stumbled upon one of these calls.

 > Now check this one #33655, it sounds a little like this one too, but for
 the 14530 it's ok. I mean, if we really want to display the new messages,
 ok, but why all in one patch? Why not one by one when someone touche
 something related to, like when we do coding standards.

 Core has said that refactoring for the sake of coding standards is not
 something we'd do. In this case, IMO, we're looking at enhancing the user
 experience by providing something more useful for an error message besides
 simply "Cheatin' Uh?". Huge enhancement? I admit, no. :)

--
Ticket URL: <https://core.trac.wordpress.org/ticket/14530#comment:75>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list