-
Notifications
You must be signed in to change notification settings - Fork 138
Closed
Labels
InfrastructureIssues for the overall performance plugin infrastructureIssues for the overall performance plugin infrastructureNeeds DevAnything that requires development (e.g. a pull request)Anything that requires development (e.g. a pull request)[Type] BugAn existing feature is brokenAn existing feature is broken
Description
Bug Description
As highlighted by one user in the support forums, there is a conflict between the Performance Lab generated object-cache.php file and the same file generated by third party plugins.
The expected behavior with an additional object-cache.php file generated by another plugin (if the PL plugin is installed first):
- The PL plugin renames the third party plugins object-cache.php to object-cache-plst-orig.php
- The PL plugin then loads it's own file, while also loading the object-cache-plst-orig.php file
Steps to reproduce
- Install the PL plugin
- Check that that object-cache.php file exists within the sites wp-content directory
- Install and active W3 Total Cache
- Within the W3 Total cache settings enable Object Caching (Performance > General > Object Cache > Object Cache > Enable)
- After enabling object caching within the W3 Total Cache settings a notice will appear recognising the conflict. You can then choose to allow W3 Total Cache to remove the PL inserted object-cache.php file. If doing so, the PL file is removed.
The same issue can be found if using LiteSpeed Cache and applying Object Caching (ListeSpeed Cache > Cache > Object > Object Cache > ON). For this plugin there is no conflict highlighted, instead the PL file is removed (recording of experience)
eF0WdP12Tn.mp4
Metadata
Metadata
Assignees
Labels
InfrastructureIssues for the overall performance plugin infrastructureIssues for the overall performance plugin infrastructureNeeds DevAnything that requires development (e.g. a pull request)Anything that requires development (e.g. a pull request)[Type] BugAn existing feature is brokenAn existing feature is broken