<plugin_name> detected an advanced-cache.php file in the wp-content directory. It seems that this is not the <plugin_name> advanced-cache.php file. Please remove this file and disable any other caching plugins to use this <plugin_name>.

[jeffreycooper]

How to Reproduce

Simply install and activate two cache plugins that use advanced-cache.php file from the admin dashboard one after another.

Isn't that time to change how WordPress use the advanced-cache.php file? Why not make wp-settings.php file to look for:

/wp-content/*-advanced-cache.php

In this way cache plugin developers will be able to create file with their name and functionality such as:

/wp-content/<plugin_name>-advanced-cache.php

In this way there will be no file replacing/removing and etc. and the whole plugin fight on who to use the advanced-cache.php file will be resolved. There will be no problem to have:

/wp-content/<my_plugin>-advanced-cache.php
/wp-content/<your_plugin>-advanced-cache.php
/wp-content/<our_plugin>-advanced-cache.php

The other possible (with eventually slower processing) solution is the advanced-cache.php file to be searched for in all of the plugins directory:

/wp-content/plugins/*

In this way each plugin can store their advanced-cache.php file in their own plugin root folder:

/wp-content/plugins/<my_plugin>/advanced-cache.php
/wp-content/plugins/<your_plugin>/advanced-cache.php
/wp-content/plugins/<our_plugin>/advanced-cache.php

And again this will be resolved. Any ideas on that?

Thanks in advance.

[johnbillion]

Thanks for the report @jeffreycooper. What's your use case for having two different plugins active that both use advanced-cache.php?

[jeffreycooper]

Hello @johnbillion and @SergeyBiryukov ,

Thank you for the edits (first ticket here) on the tickets and the attention to it.

HummingBird and W3TC for example. Another example is Cache Enabler and LiteSpeed cache plugins. These are the ones that got my attention the most. However I am sure there are many other cases for this issue too.