Autoconfig won't enable extension by default
We have pointed the thunderbird preferences to our own webservice that generates user based configuration files.
ProgramFiles/Mozilla Thunderbird/default/pref/autoconfig: pref("general.config.filename", "defaults/pref/ourconfig.cfg");
and
in ProgramFiles/Mozilla Thunderbird/default/pref/ourconfig.cfg var env_user = getenv("USERNAME");
lockPref("autoadmin.global_config_url", "http://ourserver/"+env_user);
Ourserver generates a configuration. This works great. Only Hickup we have that our extensions aren't enabled (they sit in the extension folder) and get installed by profile creation. If I curl the configuration and put it directly in to ourconfig.cfg the addons are enabled by default. What am I missing? Ty for your time. Joe
All Replies (1)
This is way above my abilities and knowledge, but my reading of autoconfiguration is that it is intended only for account set-up; I can't see that it was intended to be used to manage extensions and so forth. Have you seen any documentation that says otherwise?
Endret