Timo

Hi Kathrin,

I think this is related to the templates you are using. The ones included may not be perfect for every use case or theme. You can create your own templates or adapt the provided ones to your needs.

We can discuss your request in detail in a support ticket if you want: https://www.wp-amazon-plugin.com/support/

Regards,
Timo

Hi Kathrin,

ok, thanks for your feedback. I am glad you got it working. If you have any questions, please let me know.

Regards,
Timo

Ok, cool. Thanks for your feedback. I will try to get it working locally with the next update. ASA2 is working with this local setup btw ??

Thank you for your request. I am not sure if this is the complete error message. Are there any more details? If you want, you may create a support ticket at https://www.wp-amazon-plugin.com/support/ so we can discuss everything about your API account details.

Hi Steven, ok cool. Thanks for the details.

Just in case, I will include the hook for my shortcodes in my next update. ??

Yes, this is right. That’s why with ASA2 you can create Amazon products without PA API in the beginning and sync them later on when your account is activated.

You can learn more about this feature here: https://docs.getasa2.com/create_amazon_product_without_api.html

Let me know if you are interested.

Hi Steven,

hooking into the ez_toc_strip_shortcodes_tagnames filter is the solution I already recommended Mario to add in the functions.php, like this:

add_filter('ez_toc_strip_shortcodes_tagnames', function ($tags_to_remove) {
    return array_merge($tags_to_remove, [
	'asa2',
	'asa2_img',
	'asa2_collection',
	'asa2_textlink',
	'asa2_smart_collection',
	'asa2_keywords',
    ]);
});

But what I don’t really understand: why does another plugin have to care that its own shortcodes still work? Shouldn’t your plugin do that itself or does your plugin not know about other shortcodes at this point? Maybe you can explain the context, I don’t doubt that you have a reason for it. ??

Regards,
Timo

• This reply was modified 3 years, 6 months ago by Timo.
• This reply was modified 3 years, 6 months ago by Timo.
• This reply was modified 3 years, 6 months ago by Timo.
• This reply was modified 3 years, 6 months ago by Timo.
• This reply was modified 3 years, 6 months ago by Timo.

Hi and thanks for your request.

This error is actually always explained by the fact that the access data is incorrect. Can you please check again if your “Access Key ID” or “Secret Access Key” are correct and that there are no copy & paste issues?

Hi John,

Thanks for pointing this out. It has been fixed with the new update (version 1.4.15).

Hi Andre,
thank you for your request. Have you check this FAQ entry already? https://bitly.com/psn-multiple-emails

Hi Emanuel,

thank you for your request. In such cases, it is recommended to create a debug rule in PSN and run through the use case. From the debug information you get in the best case information why it does not work as thought.

This documentation page shows how to create a debug rule with PSN: https://docs.ifeelweb.de/post-status-notifier/rules.html#debug-rule

Hi, sorry for my late reply. This is the free version support ??

Translating texts in ASA1 can be done in the HTML templates directly.

ASA2 has a dedicated translation backend where you can customize the texts for each language separately, see https://docs.getasa2.com/templates_translation.html

The support response time for the Premium version is also completely another matter. ??

Hi,
thanks for your feedback.

You have already pointed it out yourself. PSN only responds to status changes of posts and comments are treated by WordPress specifically and not as posts. So unfortunately PSN does not work with comments.

Thank you for your request. If the post type and/or category appear in PSN’s rule form, Then it should actually work. Of course there can be variations in behavior when this type of post is implemented and saved by a theme. Have you tried standard posts? Is this theme freely available so that I could test it?

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. ??