HomeAboutResourcesCalendarContact
Get Resources

Community pages return a 404 after changing the base slug

MA Marco Silva 2 months 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?

2

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.

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

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

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.

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

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

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

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

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

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

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

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

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

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.

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.

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

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.

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

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.

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

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.