Ed Mullen wrote:
Paul Marwick wrote on 10/6/2014 3:50 PM:
Ed Mullen wrote:
Paul Marwick wrote on 10/6/2014 2:23 AM:
I followed the directions - used the new profile to log into a password
protected site, saved the password. But there is no <numbers>.s file
created. And no information that I can find to help me actually get the
password data from the old profile to the new one.

Passwords are in: signons.sqlite - you also want the old profile's
key3.db file, the key database for passwords

Thanks for that. Something odd going on though - still doesn't pick up
any of the passwords. I tried killing the new profile and starting
again, this time logged into a web site and saved my password. No sign
of a signons.sqlie being generated by doing so, but going into password
manager from the browser menu shows the saved password.

I'm also interested in where current versions of Seamonkey keep
bookmarks. Looking at the Firefox docs, Firefox seems to use
places.sqlite, but that doesn't seem to work with Seamonkey either.

:( I really don't want to give up on Seamonkey, but this is becoming
increasingly frustrating. Especially since the old profile works ok on
one machine, just not on the one I use most frequently.

Paul.


Well, I'm a Windows user, not Linux. Still, I think the files are the same in this case. Bookmarks are kept in places.sqlite in SM as far as I know. You might want to peruse Mozillazine ala:

<http://kb.mozillazine.org/Profile_folder_-_SeaMonkey>

Thanks for that link - it gives me some data that I hadn't found in my earlier searches, and is a bit more up-to-date than the link I found on migrating profiles.

So far as I know, the only difference is in the profile location. Can't see any reason that the files would be any different between Windows and Linux. In Linux, the profile is stored in a hidden (. prefix) directory called mozilla/seamonkey/<profile-name> under the users' home directory, but it certainly looks as though the profile files are the same.

I've made a bit more progress. First, I've managed to get the bookmarks correctly picked up. Turns out its not only places.sqlite you need. There are two other files - places.sqlite-shm and places.sqlite-wal. If those are also copied over, bookmarks work. I missed them when I first tried to move things - they seem to be changed at the end of any session and sometimes appear as places.sqlite.corrupt-???. Pity there doesn't seem to be any documentation for it....

Second is not so good. It seems that the format for the password file has changed again. Passwords are now stored in logins.json. Which, naturally, is not an sqlite file. Looking at my working version of 2.29.1, it looks as though the first (successful) launch of the new version converted from signons.sqlite. Whether there is any other way of doing it is not clear at the moment. I hope someone can give me a method of doing so....

If there isn't a method, I guess I'm going to have to archive my current 2.26 profile, start a fresh 2.26 profile, then pull in things like bookmarks and passwords, then hope that this time, it will work when "upgrading" to 2.29.1.

I've been using Seamonkey since the days of the original OS/2 mozilla suite. Tried Firefox (called Phoenix in those days?) and Thunderbird when separate applications came out, but soon went back to the suite. The last few days has brought me closer to abandoning it than ever before...

Paul.

_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to