HomeAboutResourcesCalendarContact
Get Resources

Reply count off by one after deleting a reply

JA Jamal Reed 4 weeks ago Resolved

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.

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

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

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

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.

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.

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

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

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

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

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.

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.

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.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

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

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

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

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