boostwpcom

We heard from another user that AAWP released a fix that no longer creates an issue with our plugin. Perhaps they used the fix above or found another work around.

Closing this now.

Thank you so much for your patience everyone. We would have preferred not to go through this time-consuming PA API 4.0 to PA API 5.0 upgrade but I believe we’re finally there.

We identified an issue in their code and are doing our best to pass it onto them now. In case they see this or if another AAWP user wants to point it out. This is the issue. I’m copy-pasting from our developer:

They are not appropriately using an autoloader for their vendor packages. They’re explicitly requiring function files for some reason.

They should change this block:

if ( ! function_exists( 'GuzzleHttp\choose_handler' ) )
    require_once _DIR_ . '/vendor/amazon-paapi5/vendor/guzzlehttp/guzzle/src/functions.php';

if ( ! function_exists( '\GuzzleHttp\Psr7\build_query' ) )
    require_once _DIR_ . '/vendor/amazon-paapi5/vendor/guzzlehttp/psr7/src/functions.php';

if ( ! function_exists( '\Promise\promise_for' ) )
    require_once _DIR_ . '/vendor/amazon-paapi5/vendor/guzzlehttp/promises/src/functions.php';

To be this instead:

if ( ! function_exists( 'GuzzleHttp\choose_handler' ) )
    require_once _DIR_ . '/vendor/amazon-paapi5/vendor/guzzlehttp/guzzle/src/functions_include.php';

if ( ! function_exists( '\GuzzleHttp\Psr7\build_query' ) )
    require_once _DIR_ . '/vendor/amazon-paapi5/vendor/guzzlehttp/psr7/src/functions_include.php';

if ( ! function_exists( '\Promise\promise_for' ) )
    require_once _DIR_ . '/vendor/amazon-paapi5/vendor/guzzlehttp/promises/src/functions_include.php';

• This reply was modified 5 years, 4 months ago by boostwpcom.
• This reply was modified 5 years, 4 months ago by boostwpcom.

We are looking into this. It looks like they made an update to their plugin that is creating a conflict with ours as well.

I don’t know your support ticket in particular, but if you share that number here I can at least look through the case history personally to see where we failed you so that we can try to do better moving forward.

In either case, I wish you the best.

The bulk of your complaint is about an Amazon limitation that we have no control over. When customers purchase the pro version if they find they are unable to use the product advertising API and they want a refund, we provide it. I’m not sure what happened in your specific case perhaps you bought well before they made the API change. Not having a US account is irrelevant. We have users that just use Amazon UK for instance. If you want to reply to your old ticket, I’ll personally assist if I am able, but if you aren’t successfully driving sales as an Amazon affiliate they won’t let you use the API.

My main point here is that a 1-star review with the first thing you cited in your review as Amazon limiting their API is completely unfair because it is.

I already commented re: AMP

In any case, I wish you the best. If you still want help, I will give it.

Hello @stretl

It’s pretty unfair to leave us a 1-star review based on the limitations of an Amazon Product Advertising API that we have no control over.

Here’s the link to Amazon’s documentation that outlines how the number of requests is based on the amount of revenue you drive as an Amazon affiliate:
https://webservices.amazon.com/paapi5/documentation/troubleshooting/api-rates.html

We updated our plugin to support the new PA API 5.0 because Amazon has ceased support for PA API 4.0 and killed it off so the only way to use the product advertising API from Amazon is to use their new API which we updated our plugin to support.

Trust me, if it were up to us, we would prefer that Amazon does not restrict affiliates from using their API because it reduces the amount of people that can use our plugin.

In any case, I don’t think this is a fair review as we can’t control the restrictions that Amazon places on the API. We will look into the AMP error though.

Thanks so much!

You’re very welcome ??

Happy we were able to help.

You can turn off our link localization and simply upload the OneLink code to the site. That may work but I can’t say for sure. We will likely have changes to our link localization technology in a future new major version release.

I’m not sure regarding the other plugin you referenced though. The goal would be for EasyAzon to meet all of your needs so if there is stuff you see in other plugins that we’re missing I would appreciate the feedback.

Please email me us direct to share that

Hello Roberto, I’m sorry for the delayed reply here. Our premium support is typically answered within 24 business hours so if there was something missed, I apologize for that.

If you reply to your support thread I’d be happy to help assist with the issue that you had experienced.

You’re an easyazon premium customer, please email our support team so that we can get you access to the latest version of easyazon pro that was also upgraded to support the new product advertising API 5.0.

I will watch for your email.

Also, please see this thread for why we had to make this update (short version: Amazon is requiring everyone to upgrade to PA API 5.0)
https://www.ads-software.com/support/topic/fyi-product-advertising-api-5-0-support-added-to-4-0-24/

• This reply was modified 5 years, 4 months ago by boostwpcom.

The reason why your links broke is because you need to migrate to Amazon’s new product advertising API 5.0.

This is a requirement of Amazon and what we’ve done is upgrade EasyAzon to use the new product advertising API 5.0 version.

See this thread created earlier this week that explains how to upgrade to the new API:
https://www.ads-software.com/support/topic/fyi-product-advertising-api-5-0-support-added-to-4-0-24/

Per Amazon:

PA API 4 access will shutdown on October 31, 2019.

So yes, you could use the old version of EasyAzon for a couple more days but you do need to upgrade. If you follow the steps shown on the thread above that should resolve the issue.

I’m personally monitoring the support threads here on www.ads-software.com to ensure a smooth transition as possible, but we have upgraded EasyAzon to support the new PA API 5.0 that Amazon has released and requires everyone to use moving forward.

I’m going to mark this as resolved. We’ve been monitoring the other support channels and everything looks good so far. We also pushed another new update to address a minor unrelated fix.

If this isn’t working for you, please reply again here and I’ll be happy to help.

Hey Victor,

I just confirmed this should be resolved now and I’m very sorry again for the initial issue. To close the loop, if you get a chance to reply to confirm everything is good to go that would be great.

Thanks