Hi,
I see.
Please try the development version 5.3.6b01 which should fix that issue.
Thank you for the report.
Thanks for the fast respond. I will test it.
In the new plugin-version, there are still bad entries in the database cache.
remained_time
86268
charset
modified_time
2023-12-08 10:11:28
expiration_time
2023-12-09 10:11:28
request_uri
https://ws-eu.amazon-adsystem.com/widgets/q?SearchIndex=All&multipageStart=0&multipageCount=20&Operation=GetResults&Keywords=B00NI5O19K&TemplateId=MobileSearchResults&ServiceVersion=20070822&MarketPlace=DE
name
AAL_e4fa61650853fba2bd8d7e064bdc02d6
_cache_duration
(null)
_now
1702030420
_modified_timestamp
1702030288
_expiration_timestamp
1702116688CacheVorschauAnsicht
headers
*data
date
Fri, 08 Dec 2023 10:11:28 GMT
server
Server
content-encoding
gzip
content-length
0
vary
User-Agent
response
code
200
message
OK
cookies
filename
(null)
body
Can you try 5.3.6b02 then?
And you want to add the following code in your functions.php file. Increase the part 50 in the below code if you still get the issue.
add_filter( 'aal_filter_max_attempts_of_sitestripe_api_requests', function( $max ) { return 50; } );
Thank you. Yes, of course I test this version.
Test ist running. Can the plugin throw an error in the Error tab when returning empty output from Amazon?
The plugin does not log such cases by default because the status code 200 means it is the response that the server wants to provide, meaning it is not an error.
You can add your custom error messages by adding the code below to your functions.php file. Not tested.
add_filter( 'aal_filter_http_request_set_cache', function( $response, $cache_name, $charset, $cache_duration, $url ) {
if ( 200 !== ( integer ) wp_remote_retrieve_response_code( $response )
|| '' !== wp_remote_retrieve_body( $response )
) {
return $response;
}
new AmazonAutoLinks_Error(
'HTTP_REQUEST_MY_CUSTOM_ERROR',
'The HTTP response is empty while the status code is 200.',
[ 'url' => $url, 'cache_name' => $cache_name ]
);
return $response;
}, 10, 5 );
Thanks,
i’m testing the new version of the plugin with your code above, to see how often the error is still present.
