While working with a new project, I noticed that you can't enable/disable themes through context but in theory it would be an almost identical process to enabling/disabling modules so it should be relatively easy to support.

Comments

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

Yes and no.

Themes don't actually need to be enabled to be used, although it is generally recommended to do so.
To actually set the default theme, there are plenty of other context modules that would be better suited.

thedavidmeister’s picture

thedavidmeister commented

Themes don't actually need to be enabled to be used, although it is generally recommended to do so.

Yes, well, it would be easy to support so why not? Enabling/Disabling themes is a concept that will likely mature in the future, there are a bunch of issues being worked on in core to flesh out what it means to "enable" a theme, including potentially dependencies on modules and whatnot...

To actually set the default theme, there are plenty of other context modules that would be better suited.

I wasn't thinking of setting the default theme here, you're right that there are other ways to do this.

thedavidmeister’s picture

thedavidmeister commented
Related issues: +#1067408: Themes do not have an installation status

I thought I'd link to #1067408: Themes do not have an installation status that provides some insight into where enabled/disabled functionality for themes is heading in Core.

markhalliwell’s picture

markhalliwell
Primary language English
commented
Status: Active » Closed (won't fix)
Related issues: +#1199946: Disabled modules are broken beyond repair so the "disable" functionality needs to be removed

Themes shouldn't be an exception, we should follow the same decisions made about modules.

https://www.drupal.org/node/2193013
https://www.drupal.org/node/2225029