I’m sorry to hear you’ve run into issues.
I tried leaving 2 comments on your latest post, and they seem to be attached to the right post so far, although Jetpack is currently active:
http://i.wpne.ws/f2uE
Do you still experience issues on your end?
Thread Starter
grenow
(@grenow)
Thanks for looking at this. I’ll let you know as soon as someone comments…
Thread Starter
grenow
(@grenow)
OK – a tame reader has posted a test comment under the current top post (got a screenshot to prove it), but it has appeared under the old post. So – definitely something going on…
Thread Starter
grenow
(@grenow)
Incidentally, in testing yesterday, if I used the WP setting to turn off comments on posts over 14 days old, attempting to comment under the top post got a “post closed” warning…
Could you check if that reader commented using a Facebook, Twitter, Google+, or WordPress.com account? You should be able to find that out in the Comments menu, based on the different fields.
Thread Starter
grenow
(@grenow)
He was using his account at Hot Topic, not one of those other services. He sent me a screenshot showing that.
I have helpful readers… 😉
Thread Starter
grenow
(@grenow)
Incidentally – the theme also seems to have a problem with long comments. Posting a long comment “loses” the post comment button – it doesn’t scroll back as it should. But that’s probably better left to another place…
He was using his account at Hot Topic, not one of those other services. He sent me a screenshot showing that.
Thanks for the extra details! I’m not sure why I can’t reproduce the issue with my own account on your site. How about you? It seems you’ve been able to comment on that post without any issues?
Could you ask your reader what browser they use, and what was the URL of the page they were commenting on? I wonder if somehow a specific parameter at the end of the URL might mess things up.
the theme also seems to have a problem with long comments. Posting a long comment “loses” the post comment button
Yes, that’s a known issue, unfortunately. We’ll get that fixed.
Thread Starter
grenow
(@grenow)
Here’s the screenshot provided. Looks like Chrome on Windows to me, and the URL is the plain vanilla post page.
Is there some way that WP/Jetpack is misreading the post ID, dropping the last three digits of the new post?
Thread Starter
grenow
(@grenow)
By the way, it’s not just one reader: same thing has happened with at least three.
Is there some way that WP/Jetpack is misreading the post ID, dropping the last three digits of the new post?
That must be what’s happening, but I’m not sure how, and why it only happens to a subset of users.
Sorry for the upcoming comment spam; I’ll be running some more tests in the next few minutes, if that’s okay with you.
Thread Starter
grenow
(@grenow)
…and not just with the top post…
Thread Starter
grenow
(@grenow)
Fine by me. Anything to get it all working again!
It looks like I was finally able to reproduce.
Would you mind opening comments to non logged in users for a few minutes? I’d like to run an additional test, but I’d need to be able to comment while logged out of the account I created on your site.
Thanks!
(@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/