Problem/Motivation
Theme Operations are the two links that get added to every theme on the system themes page - namely "Enable" and "Enable and Set as Default", after a theme is enabled you get "Disable" and "Set as Default".
These are magically added to all themes - however not all themes are suitable as default themes - in some cases you want a theme that acts like a base theme that holds configuration for all it's sub themes, or provides other functionality but cannot or should not be run as a front end default theme.
What I would like is to be able to turn off the "Set as Default" type links.
This general idea is something that's been discussed many times over the years and something many of us base-themers would like, for example I often work on very large systems where we have multiple "base themes" with different sets of features etc, we don't want to hide them because they have configuration, but never should they be set as default.
As part of the general overhaul of installable/uninstallable themes and the theme extension system this would be a nice addition and looks like it's pretty easy to achieve.
Proposed resolution
If we had something like base: only or similar in info.yml and test on that when building these operation links?
Comments
Comment #1
dawehnerThis is more about the theme system than the extension system.