Reply count off by one after deleting a reply

JA Jamal Reed vor 4 Monaten Gelöst

Steps to reproduce: create a topic with three replies, delete one. The space listing still shows three replies on the topic.

It corrects itself after running wp jetonomy recount, so it looks like the denormalized counter isn't decremented on delete. WordPress 6.9, single site.

4

The importer preserves original dates and maps forums to spaces. Always run with --dry-run first to preview counts, take a database backup, then run the real import. It batches large datasets so timeouts are not a concern.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Solid breakdown. The only thing I would add is to back up before making the change — better safe than sorry.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Strong agree. Good defaults beat a wall of toggles every single time.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

Strong agree. Good defaults beat a wall of toggles every single time.

For what it is worth, the same approach works with the PMPro adapter — the membership side is identical from here.

Adding a small note: the same idea applies on mobile, just with a bit more attention to tap targets.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

Solid breakdown. The only thing I would add is to back up before making the change — better safe than sorry.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.