moving the profile from waterfox classic

[dapgo]

I had a successful migration following the steps below, I have everything working fine.

But, now I would like to remove the non used web extensions from the profile folder.
Ideas? how to automate the identification?





1) The "Profile" folder [1]

1.1 Full content/folder WF profile copied to Basilisk folder [2]
1.2 Open Basilisk
Result:
OK: Addons, bookmarks
NOK: history, cookies, form history, masterpassword
logins ( migrated only old logins, til 2017 ) ,

[1] about:support and click on "Profile Folder"
[2] (with basilisk closed)

2) Logins [1]

2.1 copy logins.json, key3.db, key4.db to Basilisk profile folder[1]
2.2 Open Basilisk
2.3 Check logins and last update date
Result: OK
[1] (with WF and Basilisk closed)

3) Backup/Restore

3.1 Install extension FEBE (exact version, febe-8.9.3.1-fx) on WF and Basilisk
3.2 Backup History, Cookies, form fill history
3.3 restoring history can take a long time and make browser unresponsive
OK: History
NOK: Formfill history, cookies (error "Backup file is not compatible with the ver of firefox currently running..")

4) Formfill history [1]
4.1 copy formhistory.sqlite to Basilisk profile folder
4.2 Open Basilisk and verify /verify content of sqlite file [2] [3]

Result OK
[1] (with Basilisk closed)
[2] i.e with "SQlite Manager" XUL extensions and, SELECT * FROM moz_formhistory
[3] SQLiteStudio for desktop is even easier than the FF extension

5) Cookies

5.1 Install an extension for cookies (advanced_cookie_manager-5.12-fx.xpi) on WF and Basilisk
5.2 On WF "EXPORT" and select a filename
5.3 On Basilisk "IMPORT" and filter/select previous file
5.4 Check/verify cookies
Result: OK


https://bloglon.blogspot.com/2023/03/mi ... assic.html

[karlkracher]

It little bit late, but one idea: Remove them in Waterfox before you move the profile. You were lucky but I think moving browser profiles from one brother to another is risky.

[dapgo]

It little bit late, but one idea: Remove them in Waterfox before you move the profile. You were lucky but I think moving browser profiles from one brother to another is risky.

It is a good idea for those that I know that they are WE but there are some that i dunno by heart.
Bu i am thinking that a method to identify the type from WF is checking the link to mozilla addons


.

[Basilisk-Dev]

I figure this is obvious, but the process you've followed is not officially supported and I personally would recommend creating a new browser profile from scratch and importing your bookmarks and reconfiguring your settings by hand. This has never been tested by devs of either of our browsers as far as I am aware and has the potential to lead to unexpected behavior. That being said, I am glad you found a process that seems to work for you.

As stated in an earlier post, I'd recommend removing the WebExtensions in Waterfox before performing this process if you plan to do this instead of creating a new profile.

[dapgo]

...
As stated in an earlier post, I'd recommend removing the WebExtensions in Waterfox before performing this process if you plan to do this instead of creating a new profile.

Yes, probably i will (my profile folder size is huge).
Once that I know that the migration was a good decision, I can start with a clean profile and backup/restore each specific type of data step by step.

[dapgo]

...
As stated in an earlier post, I'd recommend removing the WebExtensions in Waterfox before performing this process if you plan to do this instead of creating a new profile.

Yes, probably i will (my profile folder size is huge).
Once that I know that the migration was a good decision, I can start with a clean profile and backup/restore each specific type of data step by step.

I've been checking and comparing profile folders and i have realized about some tasks done by basilisk during the 1st load of the profile folder

WE xpi files have been removed/deleted from \extensions\
But an insignificant WE data is still available on extensions folders \browser-extension-data\%extensionid%

So Maybe i have nothing to do or just delete some data folders