Support » Plugin: W3 Total Cache » Conflict on object-cache.php

  • Resolved cybeardjm

    (@didierjm)


    Hi, just updated to the latest version of Performance Lab by the WordPress Performance Team and it installs an object-cache.php in wp-content with a different signature than yours, ofc creating a conflict.

    Options are: to remove the file or disable object caching.

    Sincerely
    DJM

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @didierjm

    Thank you for reaching out.

    I’ve tested this and indeed the mentioned plugin does add the object-cache.php to the wp-content folder. Unfortunately, the only solution for this is to remove the file added by Performance Lab, as W3 Total Cache needs this or Object Caching if enabled of course.

    Just to confirm, this was added in the latest release?

    Thanks!

    Thread Starter cybeardjm

    (@didierjm)

    Thx Marko, absolutely, with the latest release of Performance Lab last night.

    On their side, they’re denying… See thread here. Might be you should confirm your tests.

    I tried many things, and finally had to rename their file.

    Sincerely

    DJM

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @didierjm

    Thank you for your feedback. It appears that they did not test this with the Object Cache enabled. It’s correct that W3TC has the file in the plugin folder: /wp-content/plugins/w3-total-cache/wp-content/object-cache.php

    This file is there so it can be added to /wp-content/ once the OC is enabled in the W3 Total Cache settings.

    As per their suggestion, you can remove their drop-in file and add the following constant in wp-config.php which will prevent this plugin from placing this file

    define( 'PERFLAB_DISABLE_OBJECT_CACHE_DROPIN', true );

    I hope this helps!

    Thread Starter cybeardjm

    (@didierjm)

    Thx @vmarko – yes, they told me I could “disable” and so on…

    But, in my view, this is bad testing on their side. I know there’s a lot of plugins, contexts and so on… making testing complex… But at least do tests with the “biggests” ones and don’t dismiss what people say by default…

    DJM

    Thread Starter cybeardjm

    (@didierjm)

    FYI issue logged on Github.

    DJM

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.