EE wrote:
Dirk Fieldhouse wrote:
On 30/01/2021 09:07, Ant wrote:
... How can I use/import my SeaMonkey's places.sqlite to use in the (lat/new)est Firefox like in the past? I don't want to use Firefox's Sync.
...

Your problem is <https://bugzilla.mozilla.org/show_bug.cgi?id=1678669> which remove Places migration from versions older than Firefox 60.

 From the accompanying commit <https://hg.mozilla.org/mozilla-central/diff/b6c11ddc2e5bcfa08c9f4f7523cec29f93ca4220/toolkit/components/places/Database.cpp>, we can see that the previous migration cut-off was schema v35/FF52 and the commit advances it to schema v43/FF52.

The simplest solution is to use FF78ESR, at least until the next ESR version replaces it. As you have chosen to be a "permanent beta" tester, that probably isn't a good answer and won't be in the long term anyway.

How about this? Have a scrap installation of FF78ESR (or later, as many Firefoxes as you need to bridge from SM 2.x to a bleeding edge FF). Close SM, copy places.sqlite to a profile in FF78ESR, run that FF with that profile, close it, copy the new places.sqlite to FF85 (or later, to a subsequent ESR and repeat until you have a compatible version).

Alternatively (for a higher degree of difficulty), reviewing the SQL that was removed in the commit (in Database::MigrateV36Up() through to Database::MigrateV43Up()) could enable one to create a SQLite database script that upgrades the schema used in places.sqlite from v35 to a compatible version.

/df

Why not just either export the bookmarks as html or back them up as sqlite from SeaMonkey and either import them or restore them into Firefox?  That would not help with the history, but the bookmarks will be preserved.


I believe places.sqlite contains more than just the bookmarks - afaik the browsing history also lands there.

--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to