It's questionable how valuable this functionality is. After all, features can be configured separately and the ability to disable/enable them group-wise does not add much value to it and makes them more complex. Extensions are a cool way to group features together and separate the code and make it more maintainable. However, disabling/enabling them adds a layer of complexity that is not required code-wise. In fact, it's extra code that you have to maintain when you write an extension because whenever you write code for your extension you currently have to check for the status of your extension through omega_extension_enabled(). We don't need that if you ask me. After all, each feature itself can be toggled on/off and we can simply check it's status through omega_theme_get_setting().

Comments

msmithcti’s picture

msmithcti CreditAttribution: msmithcti commented

I think one plus point for being able to enable/disable extensions is when it comes to the development extension. On a production site you can quickly just toggle to development tools off.

fubhy’s picture

fubhy CreditAttribution: fubhy commented

Yes, but that seems to be the only use-case. What I'd like to do is this: Set up a possible $conf override so that you can override whether or not development is enable in settings.php. Remove extension disable/enable and instead read from that variable for enabling/disabling only the development extension.

That way you can completely disable it on production by simply settings $conf['omega_development'] = FALSE. If that variable is not set, it assumes that it's enabled.

msmithcti’s picture

msmithcti CreditAttribution: msmithcti commented

Yeah, that sounds like a nice solution as it's kept in code and can be deployed (although the theme settings can be deployed also I suppose).

fubhy’s picture

fubhy CreditAttribution: fubhy commented

Yes, theme settings can be deployed but then they would be disabled for dev environments too. Allowing overrides in the settings.php is a good idea I think. I'll try that later.

fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Active » Fixed

Will keep it.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

osopolar’s picture

osopolar
Primary language German
Location 🇩🇪 GER 🌐
CreditAttribution: osopolar commented

This was not easy to find and should be better documented somewhere: To override whether an Omega extension is enabled or not add following code to your settings.php:

// Disable Omega development extension
$conf['omega_toggle_extension_development'] = FALSE;