Hi,
The situation you describe is something Fast eBay Listings can specifically manage via the ‘deferred loading’ setting (under the cosmetic & behaviour tab).
When the Deferred Loading setting is not used, then listings may be cached as part of the page via plugins such as LiteSpeed.
But, when deferred loading is enabled, only the Javascript stub to load listings is cached with the page, and so up-to-date listings will always be loaded asynchronously to the page load via Javascript.
As such, the recommendation is to set ‘Deferred loading of listings’ to ‘Always’ if you use a page caching plugin, like Litespeed. This will ensure the eBay content shown remains fresh and the initial page loading will not be slowed by the query to eBay.
Hope that helps!
Arthur
Assuming resolved, closing thread, let me know if you have any further questions.
I’ve been having issues with the plugin not showing results after 24 hours or so (they just don’t load) but I think I’ve narrowed it down to browser caching. I use Litespeed cache and when it’s set to cache in the users browser it seems to cause issues with Fast eBay Listings (FEL). I’ve turned it off and haven’t had problems yet. Hopefully it’s solved.
I also noticed a PHP error regarding FEL:
PHP 8.0 incompatibilities: FILE: cats/cat_chooser.php FOUND 1 ERRORS AND 0 WARNINGS AFFECTING 1 LINES 46 | ERROR | “$this” can no longer be used in a plain function or method since PHP 7.1.
Not sure if it makes a difference or not but thought I’d pass it along.
Hi Jay,
I suspect this is related to the WordPress Nonce used for the deferred JS loading calls. This is a time-sensitive one-time token used by your WordPress site to verify the JS call for deferred loading is valid. If your page caching is retaining this after it has expired, it will cause the deferred loading JS call to fail.
This is a common issue with page caching plugins and something I’m currently looking into a solution for.
The PHP error you found is related to the category chooser feature used within the admin dashboard. This is a secondary logging bug, but is also related to a nonce validation error. Possibly due to dashboard pages left open in a browser longer than a day, or your page caching plugin is also caching admin dashboard pages too… I’ve fixed the error logging bug nonetheless.
In summary, I should have some tweaks that will help these errors released later this week.
Best regards,
Arthur.
