Did you previously export the installed scripts?

• https://www.tampermonkey.net/faq.php

If Tampermonkey stores its scripts in local storage (indexedDB) then the extension might have lost this data. You can check the storage folder in the profile folder (storage -> default).

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

• Help -> Troubleshooting Information -> Profile Directory:
  Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder
• http://kb.mozillazine.org/Profile_folder_-_Firefox

I thank you for your help. no i did not export my scripts. otherwise, i went to the path you told me with about: profiles. Then in: C: \ Users \ ***** \ AppData \ Roaming \ Mozilla \ Firefox \ Profiles \ seasuo4e.default \ browser-extension-data

I see the folder firefox@tampermonkey.net in this folder, i have a file named: "storage.js.migrated" which is 1.81 MB in size I tried to rename this file in .txt

and looking inside, i recognized the names of my Tampermonkey scripts, so i may be lucky to get them back, but how i do not know anything about computers am novice :(

The browser-extension-data folder was used previously by Firefox to store session data. Currently this data is stored in the storage folder in IndexedDB.

See this article for instructions about how to recover extensions data.

• https://www.ghacks.net/2018/08/06/dont-downgrade-firefox-63/

thanks, i followed your indications and in : extensions.webextensions.ExtensionStorageIDB I have: extensions.webextensions.ExtensionStorageIDB.migrated.firefox@tampermonkey.net  : modifié booléen True

so the data extension of my Tampermonkey has been migrated as i have " True "

-But as my problem is still there, i followed the steps indicated in your link to remigrate the data extension of Tampermonkey :

but i block at step 7  :(  : " Open the browser console by selecting Menu > Web Developer > Browser Console or by using the shortcut Ctrl-Shift-J. "

- I can not find what is the process for re-install Tampermonkey through the browser console? :(

You install Tampermonkey in the usual way via its Add0-ons website.

• https://addons.mozilla.org/firefox/addon/tampermonkey/

The Browser Console is only used for verifying that the old Tampermonkey storage (storage.js file) has been migrated to the new indexedDB storage. You should wait until you see this message in the Browser Console. Then you can open the Tampermonkey settings to check if you have your scripts back.

I re-installed the extension tampermonkey by your link ,thanks :) and i'm happy, the option that i surrounded in red on my screenshot is re-appeared !

I have access to my scripts again but unfortunately inside it is empty, my scripts are not there anymore as you can see on my 2nd screenshot :(

but it's not a drama i will re-install my scripts in ,now that i have access to "option" again if there is no other way to find them

Hi sykranx, at the start, you had

[profile]\browser-extension-data\firefox@tampermonkey.net\storage.js.migrated

then you copied that file to

[profile]\browser-extension-data\firefox@tampermonkey.net\storage.js

so Firefox would migrated it again.

Did Firefox find the file and rename it with a .migrated file extension?

That file has your scripts, but I don't know if there is an import method you can use with that file, or whether it needs some edits first to be importable.

I'm sure other Tampermonkey users have run into issues... unfortunately, their forum at https://forum.tampermonkey.net/ is "temporarily offline" so I don't know where you could find discussions along those lines.

The article doesn't mention to reset the migration pref, so you can try to reset this pref as well as part of the steps and try again.

• extensions.webextensions.ExtensionStorageIDB.migrated.firefox@tampermonkey.net = false

I would either rename storage.js.migrated to storage.js or move storage.js.migrated to a different folder to prevent Firefox from finding this file.

• browser-extension-data\firefox@tampermonkey.net\storage.js.migrated => storage.js

thank you for your help to all -after re-installing tampermonkey, i went back to the path : C:\Users\***\AppData\Roaming\Mozilla\Firefox\Profiles\seasuo4e.default\browser-extension-data\firefox@tampermonkey.net\storage.js.migrated

and I realized that the size of my " storage.js.migrated " file has been reinitialized, reset as you can see on my screenshot, it is now at 1ko -by chance i had just before, make a backup of my " storage.js.migrated " file of 1.21mo . -I replaced it with the 1ko file -then i opened firefox but my scripts still have not reappeared.

-I have also tried your suggestion to rename storage.js.migrated => storage.js but it still does not work my scripts do not reappear

-I also tried your other suggestion, change True a False: extensions.webextensions.ExtensionStorageIDB.migrated.firefox@tampermonkey.net = false

but again, restarting firefox, nothing changes my scripts do not reappear yet as i said, i'm sure that my " storage.js.migrated " file of 1,81mo that i renamed in .txt contains all my scripts well because i recognized their name in searching in it. then i removed the .txt of course then for the file to be as before.

I think, as it is complicated, only the developer of tampermonkey could solve this problem, but if you get there, it's sure it would be great :)

I gave it a try and installed Tampermonkey in Firefox 60 ESR. I copied its browser-extension-data\firefox@tampermonkey.net folder to a Firefox 67 profile and installed Tampermonkey. This worked when I installed Tampermonkey as a fresh install (it hadn't been there before). Then I uninstalled Tampermonkey and restore storage.js and tried again to install Tampermonkey and got the same results as you reported. So apparently something was leftover from the previous install, so I tried again (restored storage.js) and this time I removed compatibility.ini as well to force to invalidate all caches. This time I got the script(s) when I reinstalled Tampermonkey, so apparently deleting compatibility.ini removed some extra leftover data that was cached.

ah ok thank you for your different tests but where do you find " compatibility.ini " ? because i want to delete it as you did but i can not find it

otherwise i looked in the browser console just now after installing tampermonkey, and i have not seen any information indicating a migration of tampermonkey :( but i do not know which tab to highlight in the browser console to see if the migration was done or not...

compatibility.ini is one of the files in the main profile folder where you also find the storage folder and the browser-extension-data folder.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

• Help -> Troubleshooting Information -> Profile Directory:
  Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder
• http://kb.mozillazine.org/Profile_folder_-_Firefox

thanks i found compatibility.ini and deleted it. then i tried renaming my "storage.js" to "storage.js.migrated". And restart firefox. my extensions were still not there.

so i did as you said next : uninstall tampermonkey and reinstall it but the problem is always there. and in : C:\Users\***\AppData\Roaming\Mozilla\Firefox\Profiles\seasuo4e.default\browser-extension-data\firefox@tampermonkey.net

-my storage.js has been reset to 1KB. I put my backup of my storage.js file at 1.81mo but the problem was still there, even trying to rename it to storage.js.migrated  :(

The file name needs to be storage.js

You first need to uninstall (remove) Tampermonkey. Then close Firefox. Make sure that the correct storage.js is in place as browser-extension-data\firefox@tampermonkey.net\storage.js Delete compatibility.ini Restart Firefox. Reinstall Tampermonkey. You can possibly check the Browser Console. Check the installed scripts.

Thanks, i followed exactly all your precise indications in the exact order.

Unfortunately my scripts still have not reappeared :(

-However, i then got some precious indications of errors in the browser console in the logs tab : ! here are the errors cited :

" Warning: attempting to write 8698 bytes to preference browser.uiCustomization.state. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes.

1559606257410 addons.xpi WARN Failed to remove temporary file C:\Users\***\AppData\Local\Temp\tmp-5fe.xpi for addon https://addons.mozilla.org/firefox/downloads/file/2691225/tampermonkey-4.9.5941-an+fx.xpi?src=dp-btn-primary: [Exception... "Component returned failure code: 0x80520015

(NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]" nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)" location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: removeTemporaryFile :: line 1248" data: no] Stack trace: removeTemporaryFile()@resource://gre/modules/addons/XPIInstall.jsm:1248

startInstall()@resource://gre/modules/addons/XPIInstall.jsm:1568 Migrating storage.local data for "Tampermonkey" (ID: firefox@tampermonkey.net, moz-extension://0e3889ee-0043-46e3-8e0d-84643efdd05d/)...

storage.local data successfully migrated to IDB Backend for "Tampermonkey" (ID: firefox@tampermonkey.net, moz-extension://0e3889ee-0043-46e3-8e0d-84643efdd05d/). Warning: attempting to write 8698 bytes to preference browser.uiCustomization.state. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes. Warning: attempting to write 8698 bytes to preference browser.uiCustomization.state. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes. "

and in the errors tab of the browser console, about tampermonkey there is also write this.... (it's in french because i'm french)  :

" Content Security Policy: Les paramètres de la page ont empêché le chargement d’une ressource à inline (« style-src »). "