If an option told to disable spell alerts or glowing buttons, they still activate if they trigger when logging in or when reloading UI.

This probably has to do with the fact that triggers are checked when the class is initialized, but at this time, the "ADDON_LOADED" event hasn't been fired yet, so the addon database hasn't been initialized, so options are set to automatically enable effects.

A possible, yet tedious solution, would be to "queue up" effects that trigger at start / reloadUI and activate them once the database is initialized.