[wp-trac] [WordPress Trac] #12816: easter egg is confusing

[WordPress Trac]

#12816: easter egg is confusing
----------------------------+-----------------------------------------------
 Reporter:  thomasq         |        Owner:          
     Type:  defect (bug)    |       Status:  reopened
 Priority:  normal          |    Milestone:          
Component:  Administration  |      Version:          
 Severity:  normal          |   Resolution:          
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by ericmann):

  * status:  closed => reopened
  * resolution:  wontfix =>


Comment:

 I'm a big fan of the easter egg, and most of my clients find it hilarious.
 But there will always be one or two "special" cases that I have to protect
 while helping them launch their sites.  Last night, one of them stumbled
 upon this easter egg, thought their site had been hacked, and freaked out.
 After several panicked emails and a couple of "holy crap my site's been
 deleted!" voicemail messages I finally got them to calm down, explained
 what happened, and helped them learn how to use post revisions properly.

 I'd never propose removing a feature from core that I enjoy.  However, if
 there was a hook that allowed me to turn it off (either the filter in the
 attached patch or by using `wp_enqueue_script()`) then I'd be able to
 silently remove the feature for these "special" clients and avoid the
 frantic "what happened" and "should I still be using WordPress"
 conversations that result.

 I see the arguments about un-obfuscating the code or removing the feature
 are moot.  But I would like a way to disable the feature without having to
 hack core to do it.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12816#comment:21>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software