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?

0

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

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

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.

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.

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

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.

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

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.

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.

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

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.

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

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

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

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

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

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

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

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

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

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.