What's the point of an "enabled" theme?

Either the theme is the active theme or it's not. What is the added value of the more "bureaucracy" of "enabled" or "disabled"?

Code that needs to look at all installed themes should be able to do so if needed. Example need is with Update status module. Otherwise, code should only use active theme.

Comments

highermath’s picture

highermath commented

The point of having enabled themes is to provide a list of themes for users who have the select theme permission. The idea is that they have the right to use themes that are enabled for that purpose, and not every installed theme.

aren cambre’s picture

aren cambre commented

That makes little sense.

If you don't want a user to select a theme, why is it on the server? Best practice in industry is that stuff that isn't used doesn't go on a production environment.

It's not as if administrators can use disabled themes. Well, they technically can, but the theme becomes enabled.

damien tournoud’s picture

damien tournoud commented
Status: Active » Closed (won't fix)

That makes perfect sense, because: (1) several instances of Drupal (in a multi-site installation) can share the same code base; (2) site owners may not want to use core themes.

So this is a won't fix on the basis of the arguments outlined here ("bureaucracy", "makes little sense"), but please also see #292253: Remove the per-user themes selection from core, that seeks the same objective, but for reasons that make a lot more sense.

aren cambre’s picture

aren cambre commented
Status: Closed (won't fix) » Closed (duplicate)

Changing to duplicate since they are so closely related.

mcrittenden’s picture

mcrittenden commented

Good proposed compromise here: http://drupal.org/node/491214#comment-1944516