Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

How to get new version to remember it has been used

  • 3 trả lời
  • 1 gặp vấn đề này
  • 6 lượt xem
  • Trả lời mới nhất được viết bởi cor-el

more options

I have FF 26.0 when I try to update to 27 or 28 or now 29 it works fine except that every time I open FF I get the "checking add-ons" pop-up and then when FF opens I get the "welcome and what's new" as though it doesn't remember I've already used the new version. There must be a setting somewhere (about:config) that forces FF to remember this is not the first time I've used the new version ...

I have FF 26.0 when I try to update to 27 or 28 or now 29 it works fine except that every time I open FF I get the "checking add-ons" pop-up and then when FF opens I get the "welcome and what's new" as though it doesn't remember I've already used the new version. There must be a setting somewhere (about:config) that forces FF to remember this is not the first time I've used the new version ...

Tất cả các câu trả lời (3)

more options

You can check for problems with preferences.

Delete a possible user.js file and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

You can use this button to go to the currently used Firefox profile folder:

  • Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
more options

Thanks ... so before I dump all my prefs here is a thought ...

IF I create a new/clean profile (firefox.exe -p) and then open FF in that profile the problem should not exist ... this could prove the solution before I delete my prefs.

And then ... what preferences do I then have to rebuild ?

more options

You can still first try to rename the prefs.js file to prefs-old.js to see if that has effect.