Omega Tools on a production site [#1538206]

I've been looking at Omega Tools a bit and it seems like it has some handy features for building new themes.

For sites that separate dev/stage/production does it make sense to keep omega_tools.module enabled in production? Are there some specific features that can be helpful in production?

Comments

Comment #1

himerus CreditAttribution: himerus commented 18 April 2012 at 14:38

I think (for now) the biggest feature that could/should/would be used on a production environment potentially is the revert theme settings feature (nothing but that simple variable delete so drupal pulls the .info file again)...

My "main" usages are limited to my development environment and staging (or in some cases production)

After generating the initial subtheme, configuring it to my heart's content, and then exporting the settings back to the .info file and reverting settings, I'm usually good to go...

A future release hopes to have some manipulations available to help make the theme settings form (specifically for Omega) much cleaner and easier to use. That would be something that would potentially be enabled on production as well, but at the same time, those types of settings probably shouldn't (by best practice) be configured on a prod environment, but instead dev/staging, and then pushing the export/reverted .info file to the repo...

I guess for the most part right now, Omega Tools lives in my sites/all/modules/development along side the devel module, coder, etc., all which don't get pushed to my prod environments...