Limited Support
Our team is currently on holiday, so support will be limited during this period. Response times may be slower than usual, and some inquiries may be delayed.
We appreciate your patience and understanding, and we’ll resume our usual support by the end of August.
Is there any solution for this problem?
I'm also interested in the solution to this issue.
Gotta say that I'm surprised that after it being flagged over 14 months ago that the solution has not been added to a plugin update.
The changes were already included in the wpDiscuz v7.3.10 - 13.01.2022. Please read the changelog here: https://wordpress.org/plugins/wpdiscuz/#developers
@asti It never worked. Even with the latest version it doesn't work either. If you have more than 50 comments, load the first 20-30 indefinitely. That's why I turned off "Lazy load comments on scrolling"
@kal,
Please create a dev/staging copy of your website in some sub-domain, make sure the problem exists and send admin details to us. You can use Duplicator to create that site.
You can send it to info[at]gvectors.com email address.
@aohagan Yes, it is exactly the same with us. And it's been like that for a year. There is no version so far to fix this problem
We've got the following error message:Â
ERROR: Either the email or password you entered is invalid.
Please check the login details again and make sure they are available for regular users.Â
@kal - given we don't want our userbase to miss out on reading comments, what steps have you been able to use to bypass this issue? (Don't get me wrong, our customers responded really positively to the switch to WP Discuz way back when, and we definitely want to retain that functionality)
@aohagan Instead of "Lazy load comments on scrolling" I use "[Load rest of all comments] Button" or one of the other options. There is no other solution to the problem. Lazy load does not work with Radis
It is fixed in the latest version from today. Thank you very much
Confirming it is working on this end too. Thanks!
Thank you for letting us know. Glad to hear that the issue is solved.
We're going to mark this thread as resolved. Feel free to open a new topic if you have further questions.
