搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 4 个回答
  • 4 人有此问题
  • 1 次查看
  • 最后回复者为 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?

被采纳的解决方案

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.

定位到答案原位置 👍 0

所有回复 (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

选择的解决方案

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.