New comments that have not yet been approved have stopped being shown on the front end. We now have to go into the dashboard to approve comments.
Hi Alex,
As you can see thousands of questions are being answered here, so we read our forum and try to help as soon as possible. You should mention the reason why this happen. What have you changed and what's new has been added in your website. This is something we can't help without proper information. Please be informative when you open a support topic to get answers as soon as possible.
Also, make sure you've deleted all caches and done Ctrl+F5 on front-end.
Also please make sure you're using the latest wpDiscuz version.
If I knew a "reason", I would have presented it.
One of our authors noted this issue on the 12th. Can I say that that is when it happened? No. Only that it is when it was noticed, but it likely is pretty close to when it happened as they go through comments regularly.
This issue affects all of out sites.
On the 11th I performed the following plugin updates.
- Easy Social Share Buttons for WordPress
You have version 5.2 installed. Update to 5.2.1. View version 5.2.1 details.
Compatibility with WordPress 4.9.1: Unknown
Subscribe conversion tracking, share booster, my template builder and more in the 4th year anniversary update - Highlight Search Terms
You have version 1.4.4 installed. Update to 1.4.5. View version 1.4.5 details.
Compatibility with WordPress 4.9.1: 100% (according to its author)
Fix: Prevent bbp_is_search() on admin triggered by Gravity Forms - MailChimp for WordPress
You have version 4.1.11 installed. Update to 4.1.12. View version 4.1.12 details.
Compatibility with WordPress 4.9.1: 100% (according to its author) - MailChimp for WordPress - Premium
You have version 3.3.22 installed. Update to 3.3.23. View version 3.3.23 details.
Compatibility with WordPress 4.9.1: 100% (according to its author) - MetaSlider
You have version 3.6.5 installed. Update to 3.6.6. View version 3.6.6 details.
Compatibility with WordPress 4.9.1: 100% (according to its author) - Redirection
You have version 2.10 installed. Update to 2.10.1. View version 2.10.1 details.
Compatibility with WordPress 4.9.1: 100% (according to its author) - UpdraftPlus - Backup/Restore
You have version 2.13.13.22 installed. Update to 2.13.16.1. View version 2.13.16.1 details.
Compatibility with WordPress 4.9.1: Unknown - User Role Editor
You have version 4.37 installed. Update to 4.38. View version 4.38 details.
Compatibility with WordPress 4.9.1: 100% (according to its author) - WCK - Custom Fields and Custom Post Types Creator
You have version 2.1.4 installed. Update to 2.1.5. View version 2.1.5 details.
Compatibility with WordPress 4.9.1: 100% (according to its author) - WP Rocket
You have version 2.10.11.1 installed. Update to 2.10.12. View version 2.10.12 details.
Compatibility with WordPress 4.9.1: Unknown - Yoast SEO
You have version 5.8 installed. Update to 5.9.3. View version 5.9.3 details.
Compatibility with WordPress 4.9.1: 100% (according to its author)
- wpDiscuz
You have version 4.1.1 installed. Update to 4.1.2. View version 4.1.2 details.
Compatibility with WordPress 4.9.1: 100% (according to its author)- Added : Display only parent comments with view replies (x) button. This increases page loading speed and keeps pages light. If visitor wants to read replies he/she just clicks on [view replies (x) ] button located on each parent comment.
- Added : Now you can control commenters by roles. You can allow/restrict access to website comment area to certain user roles.
- Added : New option “Load all comments” on first page load
- Fixed Bug : Incorrect phrases
Right now I have TwentySeventeen, wpDiscuz, wpDiscuz - Google reCAPTCHA, wpDiscuz Front-end Moderation, and nothing else activated on one staging site and the issue still persists, so in my estimation, the "reason" lies in one of the three plugins we have from you.
That is all of the information I have that I am aware of enough to provide. If you require any further information, let me know what it is.
Also, this isn't caching. I don't have any caching on the staging server and I am seeing styles from changes that cam after this issue.