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

Making WordPress.org noreply at wordpress.org
Mon Aug 5 01:14:16 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 dd32):

 Replying to [comment:2 Ipstenu]:
 > Not being able to use slug is going to mean we still face the same
 problem we have for years, which is people don’t realize you cannot have
 the slug twice... They constantly submit the same slug they use for their
 premium stuff.
 > There’s no way to do that? The slug itself is the main issue, after all.

 The slug is the main issue, but the slug is defined by the name anyway -
 so it's basically the same check at the end of the day.. just using
 slightly different sanitization methods.
 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..

 The reason that it's unable to lookup by slug is due to the significantly
 higher number of plugin slugs used vs the number of plugin names, 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 (Also why the stat is >=100 rather than 50 as
 for themes)

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

More information about the wp-meta mailing list