Community pages return a 404 after changing the base slug

Marco Silva Marco Silva 1 month ago Resolved

I changed the base slug from community to forum and now every community page 404s. The settings saved correctly.

I suspect rewrite rules — what's the right way to regenerate them?

1

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.

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.

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.

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.

Run wp jetonomy flush-rules (or visit Settings > Permalinks and save) after changing the base slug. The 404s are stale rewrite rules — regenerating them fixes it immediately.

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.

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

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

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.

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.

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.

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

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.

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.

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.

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.