Plugin conflict with W3 Total Cache

  • Resolved arnesonium

    (@arnesonium)


    4 years, 5 months ago

    Hi, I just installed the newest update and started getting fatal errors related to GuzzleHttp. This package was already being loaded by W3 Total Cache.

    Here is the error:

    
PHP Fatal error:  Cannot redeclare GuzzleHttp\\json_encode() (previously declared in /[wp-root]/wp-content/plugins/tweet-old-post/vendor/guzzlehttp/guzzle/src/functions.php:164) in /[wp-root]/wp-content/plugins/w3-total-cache/lib/Aws/GuzzleHttp/functions.php on line 323

    I’m running PHP v7.2.33.

    I had to remove Revive Old Posts to get my site working again. I hope the fix is simple!

Viewing 7 replies - 1 through 7 (of 7 total)

  • I had the same issue but with a conflict with Lasso! It also entirely broke down my website, including the dashboard.

    Plugin Contributor Uriahs Victor

    (@uriahs-victor)

    Hi there, You can revert to v8515 to fix this issue immediately, we’ll work on a release that will hopefully prevent this sort of conflict with other plugins using the same dependencies as ROP.

    You can temporarily disable the conflicting plugin, then on the ROP plugin click the “Roll back to v8.5.15” link

    Plugin Contributor Uriahs Victor

    (@uriahs-victor)

    @arnesonium Can you please send us a support ticket here? https://revive.social/direct-support/

    I can’t replicate the issue on system with W3 Total Cache. In your support ticket include a link to this thread.

    Thread Starter arnesonium

    (@arnesonium)

    @uriahs-victor I have sent a support ticket! Thank you.

    In the meantime, do you have a link to v8515? I had to delete ROP entirely, so I don’t have a way to get the “Roll Back” link in WordPress.

    Thanks!

    Plugin Contributor Uriahs Victor

    (@uriahs-victor)

    @thepoorswiss can you please try updating to the latest version of ROP and let us know if you’re still having issues?

    But before doing that, can you possibly share with me the conflict error you were receiving? The issue here seems to be a conflict between a dependency…of a dependency that ROP uses. In the OP case the Guzzle version W3 Total Cache is using is an older version so it’s conflicting

    @uriahs-victor Sure, here is the trace of the error: https://ibb.co/BVrzgm2

    In my case, it was the same error as the OP, but about another plugin (Lasso).

    Regarding the latest update, it seems to have fixed the issue for me!

    Thanks!

    Plugin Contributor Uriahs Victor

    (@uriahs-victor)

    @thepoorswiss This is because we moved the Google My Business dependency which was calling Guzzle to the pro version of the plugin.

    This means if you updated to Pro the issue would still exist, Lasso would have to look into updating their dependent libraries to prevent conflicts with plugins like ROP and others

    We’re also looking into workarounds so it wouldn’t matter whether or not other plugins have done this.

    • This reply was modified 4 years, 5 months ago by Uriahs Victor.
Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Plugin conflict with W3 Total Cache’ is closed to new replies.