Community pages return a 404 after changing the base slug

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.

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.

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

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.

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

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.

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.

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.

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 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.

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.

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.

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

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.

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

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

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

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

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.