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

Repair damaged recovery.js file?

  • 3 wótegrona
  • 1 ma toś ten problem
  • 5 naglědow
  • Slědne wótegrono wót carava23

more options

Hi, so upon restart recently my tabs from the last session weren't recovered. I have two files which contain the links: a recovery.js and a recovery.bak, both of which are very large. I'm familiar with the process of renaming them to sessionstore.js to recover the tabs, but that isn't working for either in this case.

I feel as though there must be some way to edit the files in a reader to force them to be recognized and generated when renamed. Is this possible? There are far too many for me to copy and paste from a reader.

Thanks.

Hi, so upon restart recently my tabs from the last session weren't recovered. I have two files which contain the links: a recovery.js and a recovery.bak, both of which are very large. I'm familiar with the process of renaming them to sessionstore.js to recover the tabs, but that isn't working for either in this case. I feel as though there must be some way to edit the files in a reader to force them to be recognized and generated when renamed. Is this possible? There are far too many for me to copy and paste from a reader. Thanks.

Wšykne wótegrona (3)

more options

Do you know in what way the files are corrupted?

The files will only work if it is possible to parse the content. You can test this by renaming the file and change the file extension to .json Then you can enable the built-in JSON viewer by setting devtools.jsonview.enabled to true on the about:config page and open the file in a Firefox tab.

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

cor-el said

Do you know in what way the files are corrupted? The files will only work if it is possible to parse the content. You can test this by renaming the file and change the file extension to .json Then you can enable the built-in JSON viewer by setting devtools.jsonview.enabled to true on the about:config page and open the file in a Firefox tab. 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.

Thanks for your reply.

I don't know what's wrong with the files, only that they won't restore the tabs as normally happens when renamed to sessionstore.js and placed in the relevant folder.

Changing to the .json extension didn't allow the file to be openable in a web browser. It does open in Firefox with .js attached but it's a huge mass of text. Nonethless, the information is there and it seems to me that there should, therefore, be a way to make it work?

more options

If anyone else has a solution, it would be greatly appreciated.