Allow opting into legacy backend pages per route in the admin
@Noah-Silvera is already working on this.
Since Sep 1, 2026.
- Dominant language
- Ruby
- Stars
- 5.3k
- Forks
- 1.4k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 62
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.