Theme Operations are not configurable

Created on 7 May 2014, about 11 years ago
Updated 18 July 2025, 1 day ago

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?

Remaining tasks

User interface changes

API changes

✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

theme system

Created by

πŸ‡³πŸ‡ΏNew Zealand Jeff Burnz

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024