Community guidelines — the short version

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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.

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.

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

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

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.

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.