Just found an issue when comments are lazy-loaded through ajax :
depending on how many comments par page you setup in Dashboard > Settings > DiscussionsΒ admin page, lazy-loading will load first batch on comments, then lazy load some more comments then starts loading again the first comments, again and again.
You can bypass this only by setting 0 in Break comments into pages with X on Dashboard > Settings > Discussions admin page, wehich is useless because it loads all comments at once instead of lazy loading them by batch.
Hi @willybob,
Please let us know if you use any cache plugins and SG Optimizer. Also, please leave some example URL to allow us to check the issue.Β
Hi, thanks for your answer.
We use Memcached, Opcache and WP Rocket.
Emptying all caches and or desactivating them at all does not solve the issue.
Increrasing how many comments par page you setup inΒ Dashboard > Settings > Discussions admin page to reach a significant amount which is higher than the number of comments posted in a specific post helps to avoid the duplication, but does not solve the issue.
Could you please send the admin login details to info[at]gvectors.com email address? I'll ask the developers to check the issue for you.Β
Sorry for the delay,
details sent by email
The issue comes from the caching system of your website. It has a very hard cache. Please deactivate all cache plugins and check again. If the issue doesn't solve then you have a server-side cache system. You'll need to contact the hosting support.Β
Thanks for your feedback
We narrowed down the issue to Memcached, will keep working on making it and Wpdiscuz work together.
The same happens with Redis Cache, it's not a memcached issue.
We investigated with both sides, it all comes back to a Wpdiscuz issue. Everything else works fine.
In the case of the Comments lazy loading and Load More function the WordPress native SQL codes are being executed. Each time the code works, the parameters are different, so no chance to work with that kind of caches.
At least they can provide a way to exclude the files, so it may chance to work with those plugins.
