Activate Plugin

Hi @avrahamberry1,

I’ve performed some cross-testing for us today on several of my sites which have the latest versions of WordPress, WooCommerce and our free Storefront theme as the only enabled software. When doing so I’ve not been able to replicate the behaviour which you describe with not being able to activate the Google Listings & Ads plugin.

From what you’ve described it potentially sounds like some other code on your site possibly originating from an activated plugin or theme is causing a conflict of some kind. That conflict is then causing an error that is preventing you from activating the Google Listing and Ads plugin on your website.

It may be worth looking for any fatal error logs which could have been generated when trying to enable the plugin by navigating to WooCommerce > Status > Logs. if you’re not seeing any fatal error logs I’d suggest initially carrying out a quick conflict test.

As a test, you could try deactivating all other plugins on your site leaving only WooCommerce activated and temporarily changing the theme to a theme like Storefront. With the site in that configuration, you could then try enabling the Google Listings & Ads to see if it then activates.

This test will let you know if it is indeed code from another plugin or your activated WordPress theme which is causing a conflict of some kind.

hi, thanks for the reply. the error is from the woozone amazon plugin i have and i contacted them and they said they can fix it. Maybe you know how to. Here is the error i got:

Error Details
=============
An error of type E_ERROR was caused in line 40 of the file /home1/hjckdrmy/public_html/wp-content/plugins/woozone/composer/amazon-paapi/paapi5-php-sdk/vendor/guzzlehttp/guzzle/src/HandlerStack.php. Error message: Uncaught Error: Call to undefined function GuzzleHttp\choose_handler() in /home1/hjckdrmy/public_html/wp-content/plugins/woozone/composer/amazon-paapi/paapi5-php-sdk/vendor/guzzlehttp/guzzle/src/HandlerStack.php:40
Stack trace:
#0 /home1/hjckdrmy/public_html/wp-content/plugins/woozone/composer/amazon-paapi/paapi5-php-sdk/vendor/guzzlehttp/guzzle/src/Client.php(65): GuzzleHttp\HandlerStack::create()
#1 /home1/hjckdrmy/public_html/wp-content/plugins/woozone/lib/scripts/amazon/aaAmazonWSNew.class.php(137): GuzzleHttp\Client->__construct()
#2 /home1/hjckdrmy/public_html/wp-content/plugins/woozone/lib/scripts/amazon/aaAmazonWSNew.class.php(80): aaAmazonWSNew->init(Array)
#3 /home1/hjckdrmy/public_html/wp-content/plugins/woozone/aa-framework/framework.class.php(6520): aaAmazonWSNew->__construct('AKIAJIIZPB7GQU6...', 'ZmGuahlhb/iVGxL...', 'com', 'berrysbuys0e-20')
#4 /home1/hjckdrmy/public_html/wp-content/plugins/woozone/aa-framework/helpers/amz.helper.class.php(156): WooZone->get_ws_object_new('amazon', 'new_ws', A

Hi, @avrahamberry1!

I’ve seen a similar error from other plugins before that refer to GuzzleHttp, but our developers recently released a fix for that with Google Listings and Ads version 1.1.

Can you please check which version of the plugin you have installed? If you have version 1.0, please see if updating to version 1.1 helps. You can download that latest version here: Google Listings & Ads.

hi, thanks for the reply. have version 1.1 already.

Hi there,

Just to confirm – you’ve updated to Google Listings & Ads 1.1 and are still receiving the error, or it solved the problem for you?

I just had a thought, @avrahamberry1. Do you have any caching from a plugin or from your hosting provider? The reason I ask is that your site might still be accessing a cached version of the plugin, so version 1.0.

If you have any caching, can you try flushing those and seeing if it helps?

if i do that, will it affect anything on my site, like the speed and other things. Yes, it is 1.1 and i am getting that error

Hi @avrahamberry1 ,

if i do that, will it affect anything on my site, like the speed and other things.

You may experience a slow site, but only temporarily. After you enable the cache again, the new version of the site will again be cached. Please check if you’re able to activate the extension after disabling cache.