GuzzleHttp autoloader conflicts

  • Resolved mazursv

    (@mazursv)


    3 years, 3 months ago

    Hi!

    We use guzzlehttp library in our WordPress setup. After we installed Google Listings & Ads plugin we start getting fatal errors that certain functions from GuzzleHttp namespace are undefined. I investigated this issue and found that your plugin also uses guzzle library but with namespace prefixing. And the reason why we get those fatals is because of composer autoloader uses the same hash keys for static files for original (unprefixed) and your (prefixed) versions of guzzle library. So autoloader loads your’s version of guzzle and skips our’s because it thinks that those files are the same.

    So there are two ways to fix this:
    1. Change original guzzle package name in composer.json.
    2. Change the path to src files of guzzle package.

    In both cases that will produce different hash keys in autoloader.

Viewing 1 replies (of 1 total)
  • Plugin Support Aashik P – a11n

    (@aashik)

    Hi there!

    Thank you for the added context, and proposed fix for the GuzzleHttp autoloader conflicts.

    For further discussion, can we request you to please open an issue in the repo directly so that the developers can further address this?

    You can find the repo here: https://github.com/woocommerce/google-listings-and-ads

    I’ll mark this topic as solved for now. Please feel free to open a new topic if you have any other questions.

Viewing 1 replies (of 1 total)
  • The topic ‘GuzzleHttp autoloader conflicts’ is closed to new replies.