Community pages return a 404 after changing the base slug

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

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

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

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.

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

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.

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

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

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

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.

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 deserves more votes. It is a small change with an outsized impact on day-to-day use.

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.

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.

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

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.

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

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

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

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

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

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.

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.

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