Timo

Hallo Andreas,

vielen Dank für deine Rückmeldung. Diese Frage habe ich mir auch schon oft gestellt und daher sicher gestellt, dass ASA1 und ASA2 beim Setup nur eine einzige Test-Anfrage an die API schickt, um die Gültigkeit der Zugangsdaten zu prüfen. Mit ASA2 kann man das mittlerweile auch sehr sch?n mittels API-Anfrage Statistikdiagramm sicherstellen (siehe https://bit.ly/asa2-1-14-de).

Dein beschriebenes Verhalten ist typisch für fehlerbehaftete PA API Accounts. Da steckt das Problem also Account-seitig und die Frequenz der API-Nutzung passt nicht zu den Fehlermeldungen. Daher steht im FAQ Eintrag auch der Rat, sich mit dem Amazon-Support in Verbindung zu setzen. Denn ich kenne einige F?lle wie deinen und die meisten davon haben sich wie magisch aufgel?st, nachdem beim Support auf eine Prüfung insistiert wurde. Denn die w?lzen die Probleme gerne erstmal auf die Anwenderseite ab.

Von daher w?re meine Empfehlung, dass du dich auch an den Amazon-Support wendest. Ich stehe dir gerne weiterhin mit Rat und Tat zur Seite. ??

thank you for your request. That’s a good idea. I will do that!

Hi,
that’s hard to tell without know all details. Also I’m not sure if this is possible with the lite version. Please create a ticket at https://www.ifeelweb.de/support/

Ok, cool! Thank you for sharing that with me. ??

Hi,

thank you for your request. It may help to use a more precise before status. “Anything” will match several status values before it reached status pending. Maybe try “new” as before status instead of “anything”.

I hope this will help.

Hi,
I can’t remember getting a message from you. Over the past few years, I’ve received maybe three requests concerning Elementor. So it is not a priority, especially since WordPress has its own block editor. If you need custom templates, ASA is the best tool to create them yourself, especially with ASA2 and its template syntax (https://docs.getasa2.com/template_syntax.html).

Only rel=”nofollow” is set in the ASA1 template. In my tests with WordPress 5.4.1 “norefferer” does not get set for target=”_blank” links.

If you don’t want target=”_blank” links, you can customize all of the templates included in ASA1. Check the guide to learn how to do this: https://www.wp-amazon-plugin.com/guide/

Another option is to add some custom code or use a plugin to remove the noreferrer which is set by WordPress as an security fix. Check out this article: https://wpbloggerassist.com/remove-noreferrer-in-gutenberg-from-the-latest-wordpress-update/

Sure, the easiest way to remove it, is to create your own custom template. Check the ASA1 help page to learn more about it: https://www.wp-amazon-plugin.com/usage/

In ASA2 there is an option for this and it is easy to shorten the product title, see this: https://www.wp-amazon-plugin.com/2016/13825/how-to-shorten-product-title-and-description/

I hope I was able to help you. If you still have questions, please let me know.

Hi,

thank you for your request. That’s right. Participation in Amazon Product API is reminiscent of the chicken and egg problem. The API simplifies the integration of product links, but you may only use the API once you have generated enough sales.

Until your activation I can only recommend to use Amazon Site Stripe to create affiliate links.

I am happy that my change has had the desired effect. Using “WP HTTP” is probably a good idea in your case. Unfortunately, I can’t do this easily, since the library that builds the requests for the Amazon API uses Guzzle internally. Changing that would be too complex.

Thanks for the advice. The change of the original namespace was caused by conflicts with other plugins that used a different/older version of Guzzle. Depending on which version was loaded first, different problems occurred. Therefore I decided to make the namespace unique to force the usage of the version integrated in my plugin. Composer was not designed for use in WordPress plugins ??

The second directory was mistakenly still included and got removed with the new update.

thank you for your request. Display logic with dependence on placeholder contents is unfortunately not possible with ASA1. This is an essential part of ASA2.

@fjordkommission Are you registered for the affiliate program? ?? -> https://getasa2.com/affiliate-program/

@kimsr I’m glad you chose ASA2. If you have any questions, please use the ASA2 support form: https://www.wp-amazon-plugin.com/support/

Thanks for all the details. I will let you know as soon as I will work on an improvement for this issue.