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?
Just Black & White
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?
Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.
Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.
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.
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.
I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.
Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.
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.
This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.
Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.
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.
Adding a small note: the same idea applies on mobile, just with a bit more attention to tap targets.
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.
This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.
Following this thread closely. We are about to face the exact same decision and the replies here are gold.
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.
Following this thread closely. We are about to face the exact same decision and the replies here are gold.
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.
I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
These cookies are needed for adding comments on this website.
Google's current Sign in with Google client library. It renders the Google sign-in button, or the One Tap prompt, so visitors can log in to your site with their Google account. It replaces the older Google Sign-In platform library.
Service URL: policies.google.com (opens in a new window)
These cookies are used for managing login functionality on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
GoDaddy's visitor traffic tracking, added automatically to sites hosted with GoDaddy and to sites built with GoDaddy Website Builder. It records page views, clicks, and page timing, and sends them to GoDaddy to measure traffic and site performance.
Service URL: www.godaddy.com (opens in a new window)
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
SourceBuster is used by WooCommerce for order attribution based on user source.
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Facebook Pixel is a web analytics service that tracks and reports website traffic.
Service URL: www.facebook.com (opens in a new window)
You can find more information in our Cookie Policy and Privacy Policy.
This video cannot play here.
Download it insteadNotifications