ThemeRouter 1.1.0: More Reliable Routing and Safer Menu Sync

ThemeRouter 1.1.0 focuses on routing reliability, safer classic-to-block navigation handoff, clearer settings, and stronger diagnostics. The release improves the controls teams rely on while moving a WordPress site one route at a time.

More reliable route resolution

Theme routing happens early in the WordPress request lifecycle, where page paths, custom post types, taxonomy archives, and rewrite rules can overlap. Version 1.1.0 adds regression coverage and fixes for those collision cases.

• Preserves valid custom post type archive requests when generic page or category candidates overlap.
• Covers nested archive paths such as /artists/search/.
• Fixes exact page and post type archive slug collisions so a landing page can continue through the active theme.
• Adds regression coverage for settings validation, preview authorization, invalid theme assignments, and rewrite collision behavior.

Safer Menu Sync preflight checks

A classic theme and a block theme can represent navigation differently. ThemeRouter 1.1.0 adds safer preflight handling before a classic menu is copied to block navigation and improves preservation of navigation item data.

Menu Sync should still be treated as a reviewed operation. Confirm the source menu and destination navigation, inspect the result, and keep the previous state available. It is not a bidirectional merge between independently edited navigation structures.

Clearer settings and diagnostics

• Saved routes that reference a missing or deleted theme are easier to identify.
• Status cards summarize active routes, missing themes, and fallback behavior.
• General settings use clearer spacing, route selectors, and helper text.
• Runtime controls separate Theme Preview and Caching from Debugging and Logging.
• Frontend debug access and diagnostic output are more tightly controlled.

WordPress Abilities API support

Version 1.1.0 adds support for the WordPress Abilities API on compatible WordPress versions. This provides a structured integration surface while preserving existing behavior on versions where the API is unavailable.

What to verify after upgrading

1. Configured themes still load for individual content, post type singles, post type archives, and taxonomy archives.
2. Custom archive paths and known page/archive collisions resolve to the intended route.
3. Missing or deleted themes are reported clearly in settings.
4. Menu Sync preflight identifies the intended source and destination before changes are applied.
5. Runtime and diagnostic settings match the environment policy for production.