If you have a theme fully published in your instance, any templates within those themes should be available to users from the web page or landing page creation wizard. Period. The limitation to restrict users to just templates associated with a single “active” theme is useless and causes unecessary friction.
There are many reasons why you may need multiple themes in your instance. Perhaps you have a child theme with tweaks to support another brand. Maybe you need to retain access to a legacy theme that has a few good templates you still leverage. Maybe you’re testing a change to a module or section and need to use a cloned child theme to test your updates.
Right now, in order for a user to chose a template from a non-active theme, they have to 1) go into the theme settings and toggle their other theme to active, 2) Create their page, and 3) remember to go back and reset the active theme back to the original theme. It’s a confusing waste of time. There’s literally already an “Other Templates” section you can navigate to within the landing page creation wizard, but none of your other templates from other themes appear there because only active theme pages can be selected. Defeats the whole purpose, no?
It seems like the tool is already built the way it needs to be: “Active” represents the “default” options a user sees when creating new pages. “Other Templates” then holds the published templates from non-active themes. All that needs to happen is for the active theme templates requirement to go away.
Status: Idea Submitted