Making WordPress.org

Opened 8 weeks ago

Last modified 8 weeks ago

#5667 new enhancement

Plugin Directory: Require more complex confirmation before self-closing a plugin

Reported by: Ipstenu Owned by:
Milestone: Priority: normal
Component: Plugin Directory Keywords:


Personal thoughts on how people manage to click on the 'confirm' button aside, it's becoming clear it's not enough to just have a one "Are you sure?" button prompt for people before self-closing their plugins.

Sadly the number of people 'accidentally' self-closing is increasing :(

The first thought that comes to mind is making them type in the SLUG of the plugin before they can do it (and not permitting that field to be pasted into), which I would hope mitigates this a little more.

Change History (3)

#1 @carike
8 weeks ago

How about a reason field with a minimum of 100 characters?
That way they can't really change their motivation later.

#2 @dd32
8 weeks ago

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")

#3 @Ipstenu
8 weeks ago

Good news? We had all of two people 'trying it out' since then and I had some stern words for them about not doing that as a plugin dev.

But the bad news is we have a lot of people who just don't think or slap the enter key.

My favorite was "My baby clicked it."

Note: See TracTickets for help on using tickets.