Repository navigation
Allow opting into legacy backend pages per route in the admin #6544
Description
Desired Behavior
Add configuration to allow selective use of old admin pages on a per route basis when the new admin is enabled. This will be configuration option that would be set in an initializer.
Current Behavior
You can select old or new but not choose a subset of pages to use the old admin on while having the new one enabled. (Old admin is still used when new admin doesn't implement the page currently)
Additional notes
Some stores have heavily customized old admin pages that will not easily port to the new admin. This will allow them to use the new admin while keeping their current heavily customized pages
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
Noah-Silvera commentedon Sep 1, 2026
@jarednorman
[-][Admin] Allow selective use of old admin on per page basis[/-][+]Allow opting into legacy backend pages per route in the admin[/+]Noah-Silvera commentedon Sep 9, 2026
Draft PR: #6601
Noah-Silvera commentedon Nov 6, 2026
@AlistairNorman should we close this one out?
I was thinking maybe I should also add a bit of documentation to the Solidus Docs website explaining this as part of the migration process?
benjaminwil commentedon Nov 6, 2026
I think we should close this out after the documentation has been updated. I think just adding a sentence or two and an example proc to the Transitioning from
Spree::AdmintoSolidusAdminsection of the Customizing the Backend Solidus guides article would be plenty enough at this point.