Value comp set for New Plugins Path use the same base slug comp used for another

Just to note that the way I use the plugin rewrites is:

New Plugins Path: comp
New Path for MYPLUGIN plugin: comp/plugin1
etc…

I have been using it this way the last couple of years without any problem, do you see anything wrong?

Sorry about that. We noticed on certain server types, using the same base slug ( in your case being comp ) cause a wrong rewrite interpretation by the Apache.
So please adjust the options values to avoid such scenario and the plugin will not trigger the notice anymore.

Thanks

So for example you suggest to set:

New Plugins Path: somethinotherthancomp

and keep the rest as they are:
New Path for MYPLUGIN plugin: comp/plugin1
New Path for MYPLUGIN2 plugin: comp/plugin2

Is this ok, will it work?

Edit: i just tried that it doesn’t work and it doesn’t even change it

• This reply was modified 5 years, 6 months ago by drazon.

I meant to change all base slug everywhere, including in individual plugins, in your example you should use something like this:
New Path for MYPLUGIN plugin: comp1/plugin1
New Path for MYPLUGIN2 plugin: comp2/plugin2

Hope it makes sense.

Thank you for your answer, ok understood. One more question is it a safe option to use each plugin rewrite without a base slug? Something like:

New Plugins Path: comp
New Path for MYPLUGIN plugin: plugin1
New Path for MYPLUGIN2 plugin: plugin2

You are welcome.
Sure, everything is perfectly safe, as long as the values are different for each option. Per your example, this will work just fine.

Thanks

Yeap that did the trick. I would suggest though in the plugin rewrites page to mention it because as it is now I thought that if I use my_plugins for wp-content/plugins then I have to use my_plugins base slug for each plugin meaning: my_plugins/plugin1, my_plugins/plugin2 etc…

Thank you for your support!

You are correct, the suggestions produce an ambiguity, i’ll update that area to make it clear.

Thanks