Timo

Thank you for your request. Have you activated the collections feature in the “Collections” tab in the admin section? Then this table should be created initially.

If so, perhaps the table could not be created or it was renamed, e.g. during a site migration. There can be many reasons.

If you want to create the tables manually in the database, here is the SQL. Please replace wp_ in the table name with your database prefix.

CREATE TABLE wp_asa_collection (
collection_id int(11) NOT NULL auto_increment,
collection_label varchar(190) NOT NULL,
PRIMARY KEY  (collection_id),
UNIQUE KEY collection_label (collection_label)
);

CREATE TABLE wp_asa_collection_item (
collection_item_id int(11) NOT NULL auto_increment,
collection_id int(11) NOT NULL,
collection_item_asin varchar(20) NOT NULL,
collection_item_timestamp datetime NOT NULL,
PRIMARY KEY  (collection_item_id),
UNIQUE KEY collection_item_asin (collection_id,collection_item_asin)
);

If that doesn’t help, please create a ticket at https://www.ifeelweb.de/support/

I checked the code and found that it is due to the use of lib3() in the file inc/class-custom-sidebars.php where it is first used on line 253 or 255. This lib is starting a PHP session in inc/external/wpmu-lib/inc/class-thelib.php:107 which is causing the described behavior. If I comment out the method call self::_sess_init(); on line 240, Ajax requests are processed in parallel again.

The described behavior happens on the admin pages of my plugins, which have nothing to do with custom sidebars. If your plugin requires a PHP session, it would be nice if it only used it on its own pages and would not initialize on other plugin’s pages.

thank you for your feedback. I’m glad you like ASA1! ??

Hi,

thank you for your request and sorry for the late reply. There is no global styling CSS from ASA1. The layout of the supplied templates is integrated directly into the templates.

If you use your own templates, you can either do it exactly the same way or put the CSS for your templates in an external file. There are many ways to do this, e.g. as part of the theme or via plugins that make this possible. With ASA2, you can save the CSS for a template separately from the HTML and it will only be integrated into the page once, even if the template is displayed multiple times.

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

Thank you for your feedback. The plugin has been successfully tested with WP 6.4 and there are currently no other error reports. Can you please activate the WP debug mode and see if there is an error message? Please create a ticket for this (https://www.ifeelweb.de/support/), as the error message contains server-side information that should not be made public.

You marked this request as resolved but it is not. After nearly a month after the 4.0.0 release and my error report, I am still without a backup synched to S3. I have to copy it manually which is not a solution.

Wow, that’s really a super-quick judgment you’re making here. If you look into the Amazon PA API, you’ll quickly find out that after you register, you first have to generate three legitimate sales through your links before you even get access to the API. As long as that is not the case, you will get this error from the API. It’s not the plugin’s fault.

So I would be happy if you would take back your rating and submit it again later, when you have a working API account and thus a basis for rating. It would also be advisable to ask the plugin developers for an explanation before you submit your next bad review. ??

• This reply was modified 1 year, 9 months ago by Timo.

Hi @nicoter,

thank you for your request. The problem was that due to unnecessarily strict checks for the output of the widget container and title, the CSS classes were filtered out.

This has been fixed with version 1.4.20.

The issue has been fixed with the new update (version 1.4.19).

Thanks for letting me know. I will check this and get back to you.

Thank you, I have replied. ??

Thank you for your request. In most cases, the problem indicates that the credentials are incorrect. Are you sure that you have entered the correct data on your local installation, identical to your productive site?

I’d be happy to take a closer look if you’d like. The best way to exchange more details about your installations is via a support ticket you can create here: https://www.wp-amazon-plugin.com/support/

Thank you for your request. In general, the API does not support the delivery of ratings. There is currently a field test by Amazon with a small group of users for who can access the rating data via API. ASA1 does not support rating at all but ASA2 does (see this blog post: https://bit.ly/asa2-1-15-2).

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

Thanks for your feedback.

This looks like a problem with the cache and invalid characters within a shortcode. I suspect that somewhere on your site HTML tags got into an asa shortcode, like so:
[asa]<b></b>B07QNVBML4[/asa]

And these HTML tags cause the problem when generating a unique cache token.

The quick fix would be to find this shortcode and remove the b tags from it so it only has the ASIN in it. If you then clear the ASA cache, the problem should no longer occur. This would also be recommended because the shortcode might not work that way.

The medium term solution is that I tweak the code to ignore invalid characters when writing the cache. However, this will only be available with the next update.

• This reply was modified 2 years, 9 months ago by Timo.

Thanks for your feedback. `I can agree with you on your points. Sending email is a complex issue and you may encounter different problems on each server. The current implementation was created based on years of experience with this topic, because unfortunately the most obvious way of implementation did not work in all cases. Additionally it has to be considered that this is a free version. In the premium version, some things are more advanced and have additional features.