The plugin does not consider the same page if there are any query parameters.

Hi @ofmarconi

thank you very much!

What you say is valid only for the homepage, for all other pages no matter what you have after the “?”.

The homepage is a particular case. FDP disables the entire plugins, not only the assets, and unfortunately, some plugins call the homepage for ajax activities. They should not do it, this is not a good practice, but this kind of plugin exists, and they are not a few.
For instance, imagine a certain plugin calls the homepage when the user submits a form. The URL will be something that looks like https://neomove.com.br/?name=john&surname=brown&…
Allowing query parameters for the homepage, if you disabled the contact form plugin on the homepage, and FDP disabled it when the user submits the form, the plugin that should handle the process would not run.

This is why FDP doesn’t disable any plugin on the homepage if you have query parameters in the URL.

In any case, this will be fixed in a future version.

At the moment, you can use the Custom URLs => Frontend URLs.
Use this match: https://neomove.com.br/?* and disable the same plugins you have disabled on the homepage.

Let me know if it works.

Thanks for the answer!

Got it, but how about having the same behavior as the cache plugins: https://i.postimg.cc/pdVvFKwz/image.png
(I’m even combining your plugin with this cache and I’m having very good results)

I can choose which Query Strings I will inform the plugin that is equal to /

This would make your plugin even more compatible with the “not” best practices of others.

You are welcome @ofmarconi

Life for caching plugins is a little easier.

Let’s suppose we have the URL https://your-site.com/?utm_source
You have different scenarios depending on the caching plugin and the settings they provide:

1) They don’t cache https://your-site.com/?utm_source because the query parameter
2) They cache it, but https://your-site.com/?utm_source is considered a different URL than https://your-site.com/

The second point means that if you visit https://your-site.com/ for the first time the caching plugin creates the cache for https://your-site.com/
When you visit https://your-site.com/?utm_source, it creates again the cache, this time for https://your-site.com/?utm_source, it doesn’t take it the cached https://your-site.com/.

In both cases, it’s usually not a problem for ajax calls. In the first case, the ajax call would not be cached.
In the second case ajax calls that have the same parameters usually will have also the same response. So if the response is cached usually it’s not a problem. It’s a problem when the URL includes a nonce or whatever is periodically updated. In fact, many people have this kind of problem with plugins that use nonces on the frontend.

Because most of the plugins don’t use nonces on the frontend if they call the homepage instead of the file admin-ajax.php, this problem doesn’t occur many times. But it’s not always so. Consider that caching is a lot more used than cleaning up other plugins. Many authors know that their plugin may have problems with a caching plugin if they don’t do it right, but very few authors take into account that another plugin may disable other plugins. This is why a plugin like FDP has to be more cautious.

Usually caching plugins provide you with the settings like you have shown in your picture.
But also FDP provides something similar with the Custom URLs => Frontend URLs.
If you add a row with https://neomove.com.br/?* you will match the homepage with whatever parameter. If you do it, I suggest you check all the actions that you can do on your website, like form submissions, checkouts if any, and so on.

In any case, with the next version, FDP will allow query parameters also for the homepage. It will detect ajax calls also for plugins that call the homepage.

If you want I can provide you with a beta version. Or if you prefer to wait for the official release, take into account a couple of days.

@giuse Thanks for the complete answer!

Got it, I didn’t know it was more complex, so glad we’ll have an update soon!

I would be very happy to be able to test this BETA, I just sent you an email from your website.

Thank you!

Hi @ofmarconi

you are welcome. Many thanks for your email and to test the beta version.

You can download it here: https://downloads.www.ads-software.com/plugin/freesoul-deactivate-plugins.1.8.9.1-beta.1.zip

Please, let me know if all is ok also for you with the beta version.

Hi @ofmarconi
I will close this thread. If you still need help don’t hesitate to open it again and reply.