Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toolbars keep getting reset

  • 3 wótegrona
  • 11 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót David McRitchie

more options

This is an ongoing issue after I upgraded to FF 4. I currently have 4.01 and running Vista. Every 2 days or so , when I boot the computer at start of the day and start firefox,my custom toolbar with some shortcuts would have disappeared. I have a backup of the localstore.rdf file which has the toolbar info in it and what I do is close firefox and then replace the localstore.rdf in the profile folder with my backup then after this I start firefox to see my toolbar back.

What I think is happening is firefox sometimes resets to default or currupts the localstore.rdf during boot or shutdown. What could be a possible fix for this?

Thanks

This is an ongoing issue after I upgraded to FF 4. I currently have 4.01 and running Vista. Every 2 days or so , when I boot the computer at start of the day and start firefox,my custom toolbar with some shortcuts would have disappeared. I have a backup of the localstore.rdf file which has the toolbar info in it and what I do is close firefox and then replace the localstore.rdf in the profile folder with my backup then after this I start firefox to see my toolbar back. What I think is happening is firefox sometimes resets to default or currupts the localstore.rdf during boot or shutdown. What could be a possible fix for this? Thanks

Wšykne wótegrona (3)

more options

There are some people who think the cause is specific extensions, I don't think so, I think it more likely having to do with the number of extensions and how many times they get updated, increasing the size of the localstore.rdf but there is no specific point at which it becomes bad I see it enlarge from 4KB on up to about 80KB usually failing somewhere between 20KB and 40KB.

This is a problem which goes back to Firefox 2 and got worse in 3 and 4, but does not affect most users (and you would think scarcely any developers).

I know I'm not about to give up any/many extensions myself:


current solutions:

Take a picture of your toolbars for later reference, then following directions for

It happens often enough for me that I make copies of the localstore.rdf immediately after customizing toolbars (with Firefox down, of course) so I have a copy that I can rename and restart Firefox, which is exactly what you do as well.

more options

Although the profile database can -and often times will- become corrupt the real issue is FF4+ will always refuse to remember custom toolbar setups. Therefore the basic article posted on toolbars resetting contains truth and is useful many times it ultimately is wrong since the real problem is the browser design itself. The supposed benefit of FF4+ is speed- but that also is done by making it impossible to run more than a couple of add-ons. In effect it means that if you want anything other than an incompetent Chrome imitation and you want the ability to run enough add-ons run 3.6 until they actually release a competent **cough cough** upgrade.

more options

@ apollow702,

I currently have 80 enabled extensions on FF 6.0, which is 40 times a couple of extensions. I do carefully choose my extensions largely based on functionality relative to reasonable size.

Remembering toolbar settings is what localstore.rdf is supposed to do the problem is not restricted to FF4+ this has been going on a long time. The problem most often appears when upgrading to a new version and there is a lot of toolbar and extension activity going on at those times. If somebody can come up with an solid example that makes it happen all the time the developers could work on it but it is too intermittent. Developers in general do not have many extensions, as they would interfere with their own development work. But if there is a conflict they are prepared to test interactions quickly with an a specific extension from what I've seen.