[wp-meta] [Making WordPress.org] #4656: Plugin Directory: Check for slug conflicts before accepting

Making WordPress.org noreply at wordpress.org
Mon Aug 5 22:52:11 UTC 2019

#4656: Plugin Directory: Check for slug conflicts before accepting
 Reporter:  Ipstenu           |       Owner:  dd32
     Type:  defect            |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |

Comment (by Ipstenu):

 >  I know it might seem odd, but when you exit the WordPress.org-hosted
 set of plugins you end up with 5-10 different folder names per Plugin Name
 header which requires significantly more memory to keep track of the "I
 saw this in the wild" stat

 No, not odd at all. I've seen the wild. It's horrifying!

 > The only place where checking the slug would be needed is by plugin
 reviewers, so if we "reverse" slugs to the name for the check for a
 reviewer, it should at least cover the majority of scenarios..

 True. I was just hoping to eventually automate that so it didn't rely on a
 human going to check if the slug was in-use. I'm still worried about the
 _high_ number of people who ask for specific slugs and end up shooting
 themselves in the foot. If that was some sort of auto check, it would
 lower the risk of stupid moments like a new plugin having 400,000
 installs. Right now if I change the slug of a pending plugin to akismet,
 it barks at me that the post already exists... I wouldn't be opposed to
 that check in the rename, but memory being an issue, then yeah :/ I really
 do just care about a true match though.

 > (Also why the stat is >=100 rather than 50 as for themes)

 I didn't know what Themes was and spitballed a guess :D 50 is fine.

Ticket URL: <https://meta.trac.wordpress.org/ticket/4656#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list