Get ThemeRouter
Menu
Product

How ThemeRouter WorksLearn the route-by-route workflow

FeaturesExplore routes, private preview, and controls

Route RulesTarget WordPress content precisely

Private Theme PreviewReview another theme before visitors see it

Route ControlsDraft, enable, pause, or remove a route

Use Cases

All Use CasesChoose a migration playbook

AgenciesMove approved sections into production

WooCommerce StoresPhase discovery and transaction routes

Enterprise TeamsRelease one content domain at a time

Large Content SitesMigrate content families gradually

Block ThemesModernize with control

Resources

DocumentationSetup and migration guidance

BlogPractical migration articles

Gradual Migration GuideBenefits, controls, and rollout decisions

SupportGet help with ThemeRouter

ChangelogSee product updates

Pricing

Log in
Get ThemeRouter

Need implementation help?

Send support the route, themes, environment details, and exact result you are seeing.

Contact support

Troubleshoot a Theme That Is Not Switching

Diagnose missing assignments, routing precedence, permissions, theme availability, rewrites, and caching.

Troubleshooting Updated July 26, 2026 6 min read

When the expected theme does not load, first determine whether the problem affects a private preview, a persistent assignment, or both. These paths have different permission and cache behavior.

Check the basics

  • Confirm the destination theme is installed and valid.
  • Confirm the assignment was saved to the intended resource.
  • Check whether a more specific assignment wins.
  • Test the exact public permalink, not an editor preview URL.
  • Purge page, object, browser, and edge caches.

If Preview Mode fails

  • Confirm Preview Mode is enabled.
  • Confirm you are logged in and can edit posts.
  • Generate a fresh preview link instead of reusing an expired or altered URL.
  • Check whether a security plugin strips or blocks the preview query parameter.

If a persistent assignment fails

  • Enable ThemeRouter debugging and inspect the winning decision.
  • Resave WordPress permalinks if custom rewrites recently changed.
  • Check for page, archive, and custom post type slug collisions.
  • Temporarily bypass full-page caching for the affected URL during diagnosis.
ThemeRouter Activity screen showing a filtered public route, routing status, request path, and loaded theme
Activity shows whether recent requests matched a configured route or used the active-theme fallback, and which theme loaded.

Still seeing the wrong theme?

Collect the exact route, assignments, environment versions, and debug output before opening a support request.

Prepare a support request
Previous
Next

Was this helpful?