[wp-meta] [Making WordPress.org] #5667: Plugin Directory: Require more complex confirmation before self-closing a plugin

Making WordPress.org noreply at wordpress.org
Thu Mar 18 22:38:48 UTC 2021


#5667: Plugin Directory: Require more complex confirmation before self-closing a
plugin
------------------------------+---------------------
 Reporter:  Ipstenu           |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by dd32):

 The `confirm()` that's there right now was really a last-minute "Wait,
 people are just blindly clicking it to see what will happen??", so I fully
 support adding more confirmation here, including a reason and some kind of
 "Are you really really really sure of this?" modal.

 I'm thinking we should apply the same modal to transferring the plugin to
 others.

 Perhaps for closing, when triple-confirming, we should add some text along
 the lines of `Your plugin will be disabled immediately, and only the
 WordPress.org Plugins team will be able to re-enable it. Your plugin will
 be disabled for a minimum of 1 week.` to push it home that this is not
 just something to toggle when they feel like it? (The minimum of 1 week is
 the only real addition here - and wouldn't be enforced, but should prevent
 people just "trying it out")

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5667#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list