I have seen this message intermittently when I try to search for items to add into a post or page but never on a published page.
It’s annoying considering it’s the Amazon published plugin and it doesn’t behave with the Amazon site itself!!
Waiting a second or two and then searching again works for me when writing a post but if this is happening on a published post it will not look professional and reduce the stickiness and return rate of visitors.
Would be interested to see what the issue and fix is.
I am now sure that the problems comes from the API Keys, but the Plugin does not give a valid neither useful error message. I found it because other plugin I had checks the API keys connection that is not working. “AWS Request Failed, please check keys – Error Message: AWS query failed to get a response – try again later.”
I have been trying to solve it but I do not know what else I can do, I wait for a solution from Amazon. I tried different keys, from afiliates console, from aws, deleted and created new, and none of them seem to work.
So I guess my problem comes not from the Plugin, but the Plugin do not show a correct information, so that is what would need to be fixed. Instead of saying always “you are asking too fast” it should lead to the correct problem (and solution if possible).
I have the same issue. If you find the answer, it would be great if you could share it!
I am trying to reach them everywhere. From aws they told me they can not help me more, because they do not own the Amazon Product Advertising API, they only give support to secure the connection with the keys. Affiliate program staff must explain how to set up the aws connection for the API, because the current documentation seems to be updated (https://docs.aws.amazon.com/AWSECommerceService/latest/GSG/GettingStarted.html).
But I think the new option in the affiliate console to get the keys directly there, should work (that doesn’t have any configuration at all). I guess there is a problem when you already had aws keys or something 🙁
Since I set up my account directly in the PartnerNet of Amazon, I am directly working on this with Amazon. I sent them a report at the support so I hope that will help. I made a new API which didn’t resolve the problem at all. I hope this will somehow lead to some help…
i’ve this problem…
Warning: array_values() expects parameter 1 to be array, boolean given in /membri/……../wp-content/plugins/amazon-associates-link-builder/admin/sidebar/partials/helper/aalb_credentials_helper.php on line 109
I found this and my keys seem to work there, so… What happens with the plugin, why does it not work then?
http://webservices.amazon.com/scratchpad/
Any updates so far from anyone? My plugin still doesn’t work 🙁
I tried many options last week and nothing worked. Now I tried again, I deleted all my keys. created them again, and… now they work. Maybe they solved something or it just went trough.
I receive yet the “too fast petitions” message sometimes, that is only a little annoying, but in general it seems to work now.
Ok, again. I am very pissed off and get no one answers anywhere. As I said 2 days ago, I tried again and it started working. Somehow, yesterday I went to check again…, And it started again to NOT WORK. I am in the same situation as before.
I contacted again the amazon support… And they tell me to check (again) with aws or the documentation (what I already did) or API developers documentation (what I am not trying to do, I only access with plugins).
So… Is someone going to help, please? Is there no staff from the Plugin looking at this forum? It was 2 weeks ago.
Dear user,
Sincere apologies for delayed response. We agree that we should show correct error messages. In order to help you, please provide following details:
1. Are the keys working fine on Product Advertising API scratch-pad.
If it doesn’t work there, please file your request by going through Help->ContactUs section on affiliate website( after signing in your account) & select Product Advertising API in the subject.
But, in the case above keys works on scratch-pad, please provide following details:
1. Plugin version
2. WordPress version
3. PHP version
4. Browser version
5. PHP error logs
6. Browser console log errors.
It seems that somehow the update fixed this.
