Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Does setting "browser.startup.homepage" during install lock keeping any user changed homepages?

  • 4 majibu
  • 4 wana tatizo hili
  • 1 view
  • Last reply by ragnar86

more options

When I set the page using the pref command, using the common "mozilla.cfg" method, any time a user tries to set the home page, it does not save. Instead it reverts back to the page set by pref. I can see in the users pref file that it is being correctly written, however once Firefox is completely restarted, it resets this in both the Firefox options and the users pref file. Is expected behavior or is it an issue anyone else has encountered?

When I set the page using the pref command, using the common "mozilla.cfg" method, any time a user tries to set the home page, it does not save. Instead it reverts back to the page set by pref. I can see in the users pref file that it is being correctly written, however once Firefox is completely restarted, it resets this in both the Firefox options and the users pref file. Is expected behavior or is it an issue anyone else has encountered?

Chosen solution

Thanks for your help but that still did not resolve the issue. What I have ended up doing is to edit the browserconfig.properties file found in the omni.ja\chrome\en-US\locale\branding\ folder and then copying that down to the local path. All of my other modifications performed in the Mozilla.cfg file work without issue.

Read this answer in context 👍 0

All Replies (4)

more options

this is expected behaviour, pref() only allows changes during the open session

instead try defaultPref("browser.startup.homepage", "http://example.com");

more options

Thanks for your solution. I tried applying the defaultpref, but it fails to work saying it cannot access the configuration file.

more options

mind the capital letter in defaultPref, then it should work!

more options

Suluhisho teule

Thanks for your help but that still did not resolve the issue. What I have ended up doing is to edit the browserconfig.properties file found in the omni.ja\chrome\en-US\locale\branding\ folder and then copying that down to the local path. All of my other modifications performed in the Mozilla.cfg file work without issue.