Hilfe durchsuchen

Mozilla.cfg file is not loading in my 21.0 version; how can I customize deployment?

  • 31 Antworten
  • 9 haben dieses Problem
  • 5755 Aufrufe
  • Letzte Antwort von cor-el

more options

I need to deploy a customized configuration for a limited access network, and have created a custom mozilla.cfg file. It appears as though mozilla.cfg is not being read. I have intentionally created errors in the local-settings.js file, and it will throw errors (even when it cannot find the mozilla.cfg file). When I create errors in the mozilla.cfg file, however, no errors are thrown and no changes are made to the applications configuration.

Alle Antworten (11)

more options

cor-el,

 Yes, all settings appear to be taking effect.  Taking your advice, I simplified the mozilla.cfg file to a very basic one liner that would be obvious (see below).

The change did not make any difference. When I review the about:config the below value is true.

"pref("browser.shell.checkdefaultBrowser", false);

more options

I wanted to add, I know that FF is looking for mozilla.cfg. When I change the name or remove the file, FF does give me an error that the file could not be found.

more options

I am ready am back in the office and ready to try and solve this issue. Does anyone have a solution for settings in the mozilla.cfg not taking effect?

more options

There is a leading quote in that line:

"pref("browser.shell.checkdefaultBrowser", false);

Is that quote in the real file as well or is this a typo?

See also:

more options

The leading quote is not in the file, it is a typo in the reply. Since I am able to control the home page with the local-settings.js file, my next items to address are locking the proxy settings, remove the default browser check, and prevent update checks.

more options

I'm having the same exact problem, were you ever able to get this working?

EDIT: okay at least for mine I am finally able to apply the info into firefox however I had to change my lockpref to just pref. so that's progress for me but I still need to lock it down so users can modify the settings.

maybe ill just remove the button and hope they don't know about about:config, lol.

Geändert am von JFurmanek

more options

The correct name is lockPref() (case sensitive).
The mzoilla.cfg file is run a JavaScript code, so any errors in the file will throw an exception and abort the execution.

more options

pref('general.config.obscure_value', 0); inside the js file is MANDATORY

add this and the pref/prefLock will work

more options

The default value of the general.config.obscure_value is 0 in current Firefox versions, so omitting this line shouldn't be a problem.

more options

We run firefox in an enterprise environment. lockdown of firefox was working fine in firefox 24. upgraded the installation to v25 for testing and lockdown is broken. get error loading configuration, problem seems to reside in local-settings.js

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

when i remove first line firefox loads but no mozilla.cfg is loaded.

anyone any ideas? Why does mozilla change te way configs are passed without notice (or am i reading the wrong changelogs?)

Geändert am von hkv-helpdesk

more options

If there is a problem with the mozilla.cfg file then you usually get a warning pop-up.

Did you check for problems with the mozilla.cfg file and only tried a files with the few safe lines that should work?

Which calls do you use in the mozilla.cfg file?

  1. 1
  2. 2