Member-facing changelog inside the community

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.

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.

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

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

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

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

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

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