搜索 | 用户支持

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

Learn More

Getting Started bookmark reappears after deleting

  • 4 个回答
  • 1 人有此问题
  • 9 次查看
  • 最后回复者为 MadEdric

more options

I am creating some public computers for my library. I want to delete the "Getting Started" and "Most Visited" bookmarks. While I can easily right click and delete them, after a reboot, these two bookmarks reappear. Is there a way to permanently get these two bookmarks off the bookmark toolbar? This using Windows 10 and Firefox versions 45 to 50.1

I am creating some public computers for my library. I want to delete the "Getting Started" and "Most Visited" bookmarks. While I can easily right click and delete them, after a reboot, these two bookmarks reappear. Is there a way to permanently get these two bookmarks off the bookmark toolbar? This using Windows 10 and Firefox versions 45 to 50.1

被采纳的解决方案

It is best not to copy the entire prefs.js file because the file contains a lot of data about the state of the browser, but compare the two files to see if you can isolate pref(s) that are about this problem.

定位到答案原位置 👍 1

所有回复 (4)

more options

That could if you reset the pref that makes Firefox create these default bookmarks or otherwise do not keep its value.

  • browser.bookmarks.restore_default_bookmarks = false

When this pref is true then a new set of default bookmarks will be created.

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.


more options

Thank you for the prompt reply. browser.bookmarks.restore_default_bookmarks was set to false. I noticed this problem happening about a month or so ago. A dozen computers I worked on last year which are virtually identical did not have this problem. I deleted those bookmarks and they remained deleted. Those machines run version 46. Does the about:config setting have a corresponding file that I could copy from one of the working computers?

more options

选择的解决方案

It is best not to copy the entire prefs.js file because the file contains a lot of data about the state of the browser, but compare the two files to see if you can isolate pref(s) that are about this problem.

more options

I did copy the pref.js file over (before I read your warning) and that did fix the problem. These are simple catalog computers, so not much different between each one (and we would hope they are are the same anyway). Thank you very much for your time and help.