Product changelog
ThemeRouter releases, improvements, and fixes.
Production release history from the official ThemeRouter GitHub repository, with the details teams need before updating.
Latest stable release: 1.2.0
10 production releases published
Version 1.2.0
Latest
July 29, 2026
A production release that redesigns the settings workspace, adds operational visibility and migration tools, strengthens route safeguards, and improves route-resolution performance.
Highlights
- Redesigns the Routing, Activity, Menu Sync, and Tools workspaces
- Adds searchable assignments, routing health summaries, and missing-theme safeguards
- Adds privacy-aware routing activity with CSV export and bounded storage
- Adds diagnostics, configuration import and export, cache clearing, and guarded reset tools
- Adds Elementor-aware route status and safer editor previews
- Improves route-resolution performance with lazy loading, request-local caching, and versioned object caching
- Adds Freemius support for a 14-day free trial without requiring a payment method
- Hardens routing isolation for wp-admin, AJAX, REST, cron, and Elementor Safe Mode
Compatibility requirementsThemeRouter 1.2.0 requires WordPress 6.4 or later and PHP 8.2 or later.
Version 1.1.0
July 3, 2026
A production release focused on routing reliability, safer releases, clearer settings, and a more polished administration experience.
Highlights
- Preserves valid custom post type archives when generic page or category rewrites overlap
- Adds regression coverage for nested custom post type archive paths
- Makes missing or deleted routed themes visible in settings
- Adds status cards for active routes, missing themes, and fallback behavior
- Reorganizes Advanced settings into Runtime and Diagnostics sections
- Adds WordPress Abilities API support on compatible WordPress versions
- Separates prerelease artifact generation from stable Freemius deployment
Recommended verificationRecheck assigned themes on CPT singles, CPT archives, taxonomy archives, and individual routes. Confirm missing theme assignments and review both settings tabs after updating.
Stable release history
Earlier production releases
Every stable GitHub release published before 1.1.0, newest first.
Restricted per-content ThemeRouter assignment controls to administrators in both the classic editor and block editor, with matching capability checks when rendering and saving.
Moved early theme matching into a dedicated resolver, strengthened CPT single detection before post types are registered, normalized rewrite query variables, and clarified debug collision reporting.
Introduced the frontend Debug admin-bar panel and a dedicated debugging setting, corrected CPT archive resolution, and narrowed page-versus-CPT conflicts so valid page paths keep loading.
Improved CPT single routing across rewrite and query-variable combinations, with a full request-path fallback to prevent unintended active-theme fallback.
Formalized route precedence, made exact page-versus-CPT conflicts deterministic, improved nested page detection, fixed assigned-theme resolution, and added security hardening.
Strengthened page and CPT collision handling, protected valid nested page paths, refined early rewrite matching, and introduced the route-collision precedence filter with developer documentation.
Prevented archive routing from leaking into colliding page URLs, improved custom archive detection, and protected real page routes including paged and feed variants.
The first public production release of ThemeRouter.
How to read ThemeRouter release notes
Each production entry separates new capability, changed behavior, fixes, and any action teams should take before updating.
Added
New routing, preview, workflow, or compatibility capability.
Changed
An existing behavior or interface now works differently.
Fixed
A confirmed routing, compatibility, or security issue has been corrected.
Action required
A step teams should take before or immediately after updating.