• Resolved ZeroGravity

    (@zerogravity)


    There is a Guzzlehttp conflict between BackWPup and Gravity Wiz’s Google Sheets add-on. We were getting a critical error on pages with a Gravity Form that uses the Google Sheets add-on. I disabled BackWPup and the critical error stopped happening.

    WordPress, plugins and themes are all the latest versions. GW Google Sheets was updated two weeks ago.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support BWU Support

    (@saranshwpm)

    Hello,

    Thank you for reaching out.

    I want to let you know that Guzzle HTTP related issue has been internally reported and initial testing has begun. However, fixing the dependencies is a complex task and will take some time, so I don’t have an estimated ETA at the moment.

    If there’s any update, it will be communicated.

    Sorry for the inconvenience.

    Best Regards,

    Thread Starter ZeroGravity

    (@zerogravity)

    Thanks!

    There are multiple threads on this – Here is a recommended solution from another plugin – https://deliciousbrains.com/php-scoper-namespace-composer-depencies/ hopefully you can use this and push out a release or upgrade to Guzzle 7

    For anyone having this issue – I just downloaded Guzzle 7 from https://github.com/guzzle/guzzle and I replaced the entire src directory in /plugins/backwpup/vendor/guzzlehttp/guzzle/src and it seems to have solved the issue

    I am getting this error when I upload a new version of my custom theme. Temporarily deactiveating BackWPup solves the problem. This not a frequent activity, so this workaround will work for me.

    Thanks for the proposed workaround @sflwa! Unfortunately, I’m still getting these errors:

    [09-Oct-2024 09:26:34]?1. Trying to send backup file to S3 Service?…
    [09-Oct-2024 09:26:34]?ERROR: Exception caught in Error: Call to undefined function GuzzleHttp\default_user_agent()

    I’ll continue to try messing with it, of course… perhaps there’s a path just past my fingertips… but figured I’d report here, too.

    Thread Starter ZeroGravity

    (@zerogravity)

    Not sure why this has been marked resolved as I can’t see anything in a change log that has fixed the issue. As for it needing to take some time, I mentioned the issue to Gravity Wiz as well and they had a namespace fix implemented in a couple of days.

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