Modules enabled or disabled automatically
QWhy some modules are magically enabled and other magically disabled every morning – also, is there a list of modules I should avoid?
AThere is a (short) list of modules you should avoid because of serious performance issues caused when used: Javascript Aggregator and Cookie Cache Bypass Advanced. Also, our running daily autonomous maintenance system enables some modules required to leverage all built-in performance enhancements: Path alias cache (D6 only) and RobotsTxt (D6 and D7). It also disables a few modules, which either should never be used on any live site hosted in the high performance system or are not allowed on our servers for performance reasons: DBlog, Update, Localization Update, Poormanscron, Devel, Ultimate Cron, Background Process, SuperCron, Boost crawler. Note that you can still enable and use both core DBlog and contrib Devel modules when needed – they are not “blacklisted”, but they will be disabled every morning (in the server timezone), because they should be used for debugging only, temporarily. To avoid this, you can use .temporary. or .testing. in the main domain name (alias is not enough) of the site during development – every such site is not affected by that procedure. Note that this procedure doesn’t touch the watchdog table, so all collected data are still available after re-enabling the DBlog again. This list can be updated with every new BOA release, so please check also: Supported, Enabled, Disabled – a complete list.
! Note! Since BOA-2.4.0 the .dev. mode works only for site aliases, no longer for the main site name, so .dev. keyword in the main site name will no longer exclude the site from the modules on/off procedure. We have changed this logic to avoid frequent confusion, because people tend to use .dev. in the main site name and then experience various issues when going with live domain, because the site behavior changes then. To avoid further confusion we have made it so .dev. mode is turned on only when it is used in the site alias, and not in the main site name. When used in the main site name, it behaves exactly as a live site domain, to make your workflow more predictable.