Thank you. You can switch the option back on now.
It looks like the problem is limited to logged in users on your site, while logged out from any WordPress.com account. That’s probably why we haven’t run into the issue before.
I’ll run more tests on a test site of mine and get back to you as soon as we can address this issue. In the meantime, I’m afraid I can only recommend that you either turn off Jetpack’s Comments module under Jetpack > Settings (you actually don’t really need it since your users are all logged in already), or open comments to the public like you just did.
Sorry for the inconvenience, and thanks for bearing with me during those tests. You can delete all those dummy comments now 🙂
Thread Starter
grenow
(@grenow)
That’s great Jeremy, will do as you suggest. Most of my readers have been with me for years, and their accounts precede any of this social log-in stuff… 😉
(@grenow)
10 years, 3 months ago
Hi,
I recently switched hot-topic.co.nz over to the 2016 theme, and immediately ran into a problem where all new comments were appearing under a post from 2007. Reverting to the earlier theme cured the problem. But I like 2016, so…
After a great deal of fiddling, tweaking and testing, and with a reinstall of the WordPress core (and database maintenance), it appears to be a conflict with Jetpack. Commenting works as it should with no plug ins running, and with all my usual plug ins except Jetpack, but activating Jetpack immediately restarts the problem.
Jetpack debug reports no problem. I’ve reindexed content.
One possible hint: the old post ID is 14 – current top post is 14382.
Yes, I have been running this thing for a while… 😉
https://ww.wp.xz.cn/plugins/jetpack/