hello jbryant, please see if the following blog entry might apply to your situation: http://mike.kaply.com/2013/05/13/more-major-changes-coming-in-firefox-21/

Hello Philipp,

 No, these changes do not apply to my situation.  Just for a test I moved the mozilla.cfg file to the pref folder, I received an error that the file could not be found.  All indications are that the file is checked for existence, but not read.  I try to set a specific startup page, but it continues to use the firefox default startup page.

setting the start-page this way is a bit complicated: http://mike.kaply.com/2012/08/29/setting-the-default-firefox-homepage-with-autoconfig/

Philipp,

 Maybe I am missing it, but I do not see browserconfig.properties file on the system.  And, I don't see an entry in the config.cfg file for the about:home page.

I've discovered that I can set the home page in the prefs.js file in the profile folder, however, this does not help me. I need to be able to set the home page for all users.

Ok, I have one question, is there a set of documents for FF 21.0 giving: what files are use? Where they can be found? And available settings?

I have a install.cmd file that works great, local-settings.js is in place and working along with override.ini. However, mozilla.cfg is not being read (or settings are not taking effect), proxy settings are not set among other settings.

Where did you place the local-settings.js file?

Can you post the content of the mozilla.cfg file?

This file is run as a JavaScript file with full permissions, so any errors that throw an exception makes the processing fail to complete properly.

The local-settings.js file is in the "defaults\pref" folder, and the below content is what I currently have in the mozilla.cfg file. I have another that has more switches, however, the one below is what I have been testing with to try and get it to work.

//Firefox  Settings
//
Try {

// set Firefox Default homepage
lockPref("browser.startup.homepage_override.mstone", "ignore");
lockPref("browser.startup.homepage","file:///c:/dvinst/ie/localpage.html");

// default proxy settings
lockPref("network.proxy.type", 1);
lockPref("network.proxy", 192.168.100.1);
lockPref("network.proxy.http_port", 8080);
lockPref("network.proxy.share_proxy_settings", true);

// disable default browser check
lockPref("browser.shell.checkDefaultBrowser", false);
lockPref("browser.startup.homepage_override.mstone", "ignore");

// disable password caching
lockPref("signon.rememberSignons", False);
lockPref("signon.prefillForms", False);

// disable application updates
lockPref("update_notifications.enabled", false);
lockPref("app.update.auto", False);
lockPref("app.update.enabled", false);
lockPref("app.update.service.enabled", false);

// disables the 'know your rights' button from displaying on first run 
lockPref("browser.rights.override", true);

// disables the request to send performance data from displaying
lockPref("toolkit.telemetry.prompted", false);
lockPref("toolkit.telemetry.rejected", true);

} catch(e) {
displayError("Mozilla: ", e);
}

Some remarks:

• You wrote 'Try {' with a capital.
• The value of these prefs is a string value and thus requires quotes:
  lockPref("network.proxy", 192.168.100.1);
  lockPref("network.proxy.http_port", 8080);
• true/false also need to be lowercase.

toolkit.telemetry.prompted is an integer pref as you can see on the about:config page

• lockPref("toolkit.telemetry.prompted", 2);

Note that you have this line twice:

• lockPref("browser.startup.homepage_override.mstone", "ignore");

//Firefox  Settings
//
try {

// set Firefox Default homepage
lockPref("browser.startup.homepage_override.mstone", "ignore");
lockPref("browser.startup.homepage","file:///c:/dvinst/ie/localpage.html");

// default proxy settings
lockPref("network.proxy.type", 1);
lockPref("network.proxy.http", "192.168.100.1");
lockPref("network.proxy.http_port", 8080);
lockPref("network.proxy.share_proxy_settings", true);

// disable default browser check
lockPref("browser.shell.checkDefaultBrowser", false);
//lockPref("browser.startup.homepage_override.mstone", "ignore");

// disable password caching
lockPref("signon.rememberSignons", false);
lockPref("signon.prefillForms", false);

// disable application updates
lockPref("update_notifications.enabled", false);
lockPref("app.update.auto", false);
lockPref("app.update.enabled", false);
lockPref("app.update.service.enabled", false);

// disables the 'know your rights' button from displaying on first run 
lockPref("browser.rights.override", true);

// disables the request to send performance data from displaying
lockPref("toolkit.telemetry.prompted", 2);
lockPref("toolkit.telemetry.rejected", true);

} catch(e) {
displayError("Mozilla: ", e);
}

You may want to look at the Firefox Health Report prefs as well.

• datareporting.healthreport.service.enabled
• datareporting.healthreport.uploadEnabled

cor-rel,

 Thanks, I make these changes and try them out.  Is there a way to set the homepage outside of the prefs.js in the profile?

have you gone through the link i've posted above about "Setting the Default Firefox Homepage with Autoconfig "?

edit: ok, i've gone trough it myself now & it doesn't apply when you want to lock the startpage, only when you want to set your own that should get restored when the user hits that button,,,

cor-el,

 I have made your recommended changes, however, proxy settings are still not set.

philipp,

 The only success I have had with setting the homepage is to wait for the user to open FF; the profile needs to be created first.  Then I can run a script to set the homepage in the prefs.js file.

 Is there not a single location within FF to set the configuration globally?  Or, is it the mozilla.cfg file, and it is a bug in 21.0 that the file is not being read?

mozilla.cfg IS the central location to lock preferences - when i try it with the content cor-el has posted above it all works for me as intended (except for lockPref("network.proxy.http_port", 8080); which is an integer and doesn't need quotes).

you wrote: I have made your recommended changes, however, proxy settings are still not set. - are only proxy settings not applied, and the other settings from mozilla.cfg work as intended or is nothing showing up? in the latter case please make sure that the mozilla.cfg is located in the same location as firefox.exe & that the content of \defaults\pref\local-settings.js is the same as described here: http://kb.mozillazine.org/Locking_preferences

philipp,

 Thanks for the feedback, I wish I knew the secret.  I have uninstalled, and re-installed with the same mozilla.cfg file.  I still get all of the defaults.

philipp/cor-el,

 When I load the proxy settings for each protocol in the prefs.js file the settings take.  However, it does not matter what combination I use (each protocol, or one for all) in the mozilla.cfg, the settings do not take.

I just wanted to let you know what I have seen.

would there be a way for you to upload your current local-settings.js & mozilla.cfg files onto some sort of file-locker and provide the links here (or per PM to cor-el and me)? maybe something will catch our eyes this way...

philipp,

 This was my test, I stripped everything out of mozilla.cfg to ensure that I was not running into conflicts that were not reported.

//pref("general.config.obscure_value",0); pref("general.config.filename", "mozilla.cfg");

lockPref("network.proxy.ftp", "192.168.200.1"); lockPref("network.proxy.ftp_port", 9119); lockPref("network.proxy.http", "192.168.200.1"); lockPref("network.proxy.http_port", 9119); lockPref("network.proxy.socks", "192.168.200.1"); lockPref("network.proxy.socks_port", 9119); lockPref("network.proxy.ssl", "192.168.200.1"); lockPref("network.proxy.ssl_port", 445); lockPref("network.proxy.type", 1);

it works fine for me when i put that content into \defaults\pref\local-settings.js and \mozilla.cfg here on my machine, so unfortunately there's no obvious fix that i could suggest ...

Do all other settings in the prefs.js file take?

One slight error in the mozilla.cfg file will make processing stop, so try to comment out all lines with // and re-enable them in groups to see when it stops working.