[wp-trac] Re: [WordPress Trac] #10168: Easy to update the wrong plugin by accident, if...

[WordPress Trac]

#10168: Easy to update the wrong plugin by accident, if...
-------------------------+--------------------------------------------------
 Reporter:  hakre        |       Owner:             
     Type:  enhancement  |      Status:  new        
 Priority:  normal       |   Milestone:  2.9        
Component:  Plugins      |     Version:  2.8        
 Severity:  normal       |    Keywords:  needs-patch
-------------------------+--------------------------------------------------
Changes (by hakre):

  * keywords:  => needs-patch


Comment:

 Replying to [comment:5 dd32]:
 > If people insist on a warning, Then a JS confirm is the only type I'd
 remotely support.

 That is so not taking care then. As webdev you should ever take the JS=OFF
 route first and enhance it later. So for those who have JS=ON can save one
 request.

 Infact, before making things complex, just go the same route as delete.
 For delete there actually is no JS warning. It works pretty straight
 forward. Because the principle of the implementation of the question is
 already done with the delete action and the user already knows how to deal
 with it, it is a strong argument _against_ doing things in a new way here.
 Like introducing a JS confirm.

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