wpDiscuz - WordPress Comment Plugin
Share:
Notifications
Clear all

[Solved] Numerous issues with new update

7 Posts
2 Users
0 Likes
724 Views
KitK
Posts: 6
 KitK
Topic starter
(@kitk)
Active Member
Joined: 2 years ago

Since updating to Version 7 we have had many, many issues, including but not limited to: 

 - People on certain devices cannot post at all.

 - Load more comments button causes crash.

 - Comments loading incredibly slowly/not at all.

 - Site completely freezing up.

 - Increased server loads slowing down the whole site.

Why would this be happening? We have a high comment volume (500-1000 comments per day), could that be causing problems? We have turned off other plugins (except some vital ones) and it didn't fix anything. Lazy loading made it worse. Loading ajax after page content made it worse. Using native wordpress ajax made no difference.

We will likely be rolling back, just because we need our site to function.

6 Replies
Tom
Posts: 453
 Tom
Support
(@tomson)
Reputable Member
Joined: 7 years ago

Hi @kitk

90% problems come from the cache. You should properly delete all kind of caches (plugin cache, CDN, minifiers, optimizer).

Once the website-side cache is deleted some users will still have issues on some devices because of the local device and browser cache. This is the most annoying cache. They can avoid that cache if they use incognito/private tab of their browsers or delete browser caches (press Ctrl+F5 on PC). All major updates of plugins face with such issues. The cache will be automatically deleted in a few days from all devices and browsers.

In any case we'd like to take a look on your website. You may have plugin conflicts and JS errors as well. Please lave your website URL.

And make sure you don't use old wpDiscuz addons with wpDiscuz 7. wpDiscuz 7 version requires 7.x.x versions of addons.

KitK
Posts: 6
 KitK
Topic starter
(@kitk)
Active Member
Joined: 2 years ago

On review it seems there is a conflict with "Page scroll to ID" a smooth scrolling plugin. Turning that off reduces the problems a lot, but does not totally remove them.

We purged all out caches after updating, that didn't seem to make much difference. And all our add-ons are up to date.

The site is off-guardian.org

2 Replies
Tom
 Tom
Support
(@tomson)
Joined: 7 years ago

Reputable Member
Posts: 453

@kitk,

We don't see any problem with the comment section all works fine on our PC and Mobile devices.

 

BTW, you have a site-wide JS errors from your theme main.js file. It's a little buggy and cause some errors. I recommend you contact to the theme developers and let them fix this issues:

2020 06 04 1212

Some devices and browsers may stop all front-end processes of other plugins because of this JS error, so the wpDiscuz may also be affected. But in fact all is ok when we test it.

 

Tom
 Tom
Support
(@tomson)
Joined: 7 years ago

Reputable Member
Posts: 453

Also, you're loading all comments at once. There are lots of comments, it may affect the page speed especially on mobile devices.

Please use [Load Comments] or [Load rest of all comments] pagination type:

wpDiscuz optiize comment loading speed

And set 10-20 comment thread (parent comments) per page, it'll load approx 100-200 comments if there are 10 replies in a comment thread:

wpDiscuz comment thread per page
KitK
Posts: 6
 KitK
Topic starter
(@kitk)
Active Member
Joined: 2 years ago

Yes, we tried lazy-loading the comments but it was no faster.

Now the plugin conflicts have been removed it seems to be working much better.

Although we are getting reports some users on iPhone 5 cannot post at all.

I also has a question about "regenerate vote data", what does the number in the box refer to? Is that the number of comments? Or something else? On some of our older posts the likes/dislikes are definitely still missing.

 

1 Reply
Tom
 Tom
Support
(@tomson)
Joined: 7 years ago

Reputable Member
Posts: 453

@kitk,

For the mobile, ask them to use "private" session of browsers to avoid caches.

The number of regenerate vote data process is the number of items to regenerate per request. For example, if the vote data table have 5000 rows, it updates 500 per request to avoid overloading the server during the regeneration process.

For other questions please open a new topic.

I close this issue.

Thank you.

Share: