Re: Migrating FF profiles to Seamonkey

2018-12-04 Thread Alexander Yudenitsch

Jonathan N. Little wrote, on 03 Dec 18 19:43:


Alexander Yudenitsch wrote:


I think that, for versions of SM up to 2.53 and FF up to 52.9ESR,
migrating profile data between them is possible, although just copying
all files directly may be problematic, since some of these files
(including prefs.js) contain 'physical' addresses, specific to each
program/OS, so that, to synchronize/transfer some of the data, you have
to make the necessary substitutions in the files' content.


Mostly for download file location MRUs and some extension locations, but
does not cause problems moving. Have moved profiles drag 'n drop from
Windows to Linux with no problem whatsoever and the profile paths are
very different. I think the extension paths within prefs.js get
autogenerated and get "fixed" upon first run.


Yes, I always suspected SM/FF does that, but have never seen any 
confirmation anywhere, plus I'm very wary of "autogenerated fixes" (it 
did work fine in one instance but, with several versions involving 
XP/W7-SM/FF, the chances of 'wrong guesses' shouldn't be forgotten), so 
I try to make the changes manually, editing the files involved.


--
Best,

s) Alexander Yudenitsch   



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-12-03 Thread Jonathan N. Little
Alexander Yudenitsch wrote:
> Hawker wrote, on 03 Dec 18 01:51:
> 
>> I know it is ancient, but it still seems to work.
>> Mozbackup lets you select what you back up and what parts you restore.
>> It has not be updated in years but I used it about a year ago to
>> restore a profile and it seemed to still work just fine.
>>
>> http://mozbackup.jasnapaka.com/
> 
> Yes, but I think Nuno Silva's query was a different one:
> 
>>> (...) I still have a few user profiles left in Firefox.
>>> What would be the best way to move these profiles to Seamonkey? I would
>>> like to preserve as much of the original profiles as possible
> 
> and MozBackup is for backuping to the same browser (ie, SM --> SM).
> 
> I think that, for versions of SM up to 2.53 and FF up to 52.9ESR,
> migrating profile data between them is possible, although just copying
> all files directly may be problematic, since some of these files
> (including prefs.js) contain 'physical' addresses, specific to each
> program/OS, so that, to synchronize/transfer some of the data, you have
> to make the necessary substitutions in the files' content.
> 


Mostly for download file location MRUs and some extension locations, but
does not cause problems moving. Have moved profiles drag 'n drop from
Windows to Linux with no problem whatsoever and the profile paths are
very different. I think the extension paths within prefs.js get
autogenerated and get "fixed" upon first run.

IMO moving a Seamonkey|Thunderbird|Firefox profile is so easy that
MozBackup is really not that necessary.

-- 
Take care,

Jonathan
---
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-12-03 Thread Alexander Yudenitsch

Hawker wrote, on 03 Dec 18 01:51:


I know it is ancient, but it still seems to work.
Mozbackup lets you select what you back up and what parts you restore.
It has not be updated in years but I used it about a year ago to restore 
a profile and it seemed to still work just fine.


http://mozbackup.jasnapaka.com/


Yes, but I think Nuno Silva's query was a different one:


(...) I still have a few user profiles left in Firefox.
What would be the best way to move these profiles to Seamonkey? I would
like to preserve as much of the original profiles as possible


and MozBackup is for backuping to the same browser (ie, SM --> SM).

I think that, for versions of SM up to 2.53 and FF up to 52.9ESR, 
migrating profile data between them is possible, although just copying 
all files directly may be problematic, since some of these files 
(including prefs.js) contain 'physical' addresses, specific to each 
program/OS, so that, to synchronize/transfer some of the data, you have 
to make the necessary substitutions in the files' content.


--
Best,

s) Alexander Yudenitsch   



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-12-02 Thread Hawker

I know it is ancient, but it still seems to work.
Mozbackup lets you select what you back up and what parts you restore.
It has not be updated in years but I used it about a year ago to restore 
a profile and it seemed to still work just fine.


http://mozbackup.jasnapaka.com/


On 11/26/2018 8:03 PM, Nuno Silva wrote:

Hello,

Seamonkey Navigator has been my main web browser for more than a year
now, but I still have a few user profiles left in Firefox.

What would be the best way to move these profiles to Seamonkey? I would
like to preserve as much of the original profiles as possible,
including:

- History
- Bookmarks
- Preferences
- Installed extensions, if compatible
   (there are no webextensions)
- passwords and cookies
- userContent.css

Could/should I just move the profile directories to
$HOME/.mozilla/seamonkey and add them to profiles.ini?


(Is there some way I could then disable Mail only in these migrated
profiles?)



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-28 Thread Nuno Silva
On 2018-11-28, Nuno Silva wrote:

> On 2018-11-27, Ant wrote:
>
>> On 11/27/2018 8:16 AM, EE wrote:
>>> Nuno Silva wrote:
 Hello,

 Seamonkey Navigator has been my main web browser for more than a year
 now, but I still have a few user profiles left in Firefox.
[...]
>
> Today I tried to do the migration by moving the profile directories and
> it worked. There are some settings I still have to set or tweak, but
> other than that, so far everything seems to show up in Seamonkey:
> passwords, cookies, history, even some extensions.
>
> And it feels faster than Firefox.

I should have added "... for the same web page with the same profile".

That was just a comment - I was happily surprised -; there's no proper
scientific study behind my affirmation :-)

It is also possible that some Firefox-only setting was slowing things
down...

-- 
Nuno Silva
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-28 Thread Nuno Silva
On 2018-11-27, Ant wrote:

> On 11/27/2018 8:16 AM, EE wrote:
>> Nuno Silva wrote:
>>> Hello,
>>>
>>> Seamonkey Navigator has been my main web browser for more than a year
>>> now, but I still have a few user profiles left in Firefox.
>>>
>>> What would be the best way to move these profiles to Seamonkey? I would
>>> like to preserve as much of the original profiles as possible,
>>> including:
>>>
>>> - History
>>> - Bookmarks
>>> - Preferences
>>> - Installed extensions, if compatible
>>>    (there are no webextensions)
>>> - passwords and cookies
>>> - userContent.css
>>>
>>> Could/should I just move the profile directories to
>>> $HOME/.mozilla/seamonkey and add them to profiles.ini?
>>>
>>>
>>> (Is there some way I could then disable Mail only in these migrated
>>> profiles?)
>>>
>> The file places.sqlite has history and bookmarks.  I have no idea if
>> they are cross-compatible any more, however.  Bookmarks are easy
>> enough to transfer.  Back them up or export as HTML and restore or
>> import into SeaMonkey.
>
> SM v2.49.4's old places.sqlite will work in the newer Firefox
> versions, but not in reversed. Firefox will upgrade it.
>
>
>> I imagine that some preference settings have changed, so comparing
>> them by comparing prefs.js files or from about:config would be a
>> good idea. Since SeaMonkey does newsgroups and email as well, there
>> are a lot more preference settings for it.
>>
>> If the extensions for Firefox were also written for SeaMonkey, there
>> would be no problem, but I would check install.rdf in the .xpi files
>> to make sure that they would be compatible with the target app
>> (SeaMonkey) version.  If the extensions were not written for
>> SeaMonkey, then running them through the converter website
>> (http://addonconverter.fotokraina.com/) might be able to fix them. 
>> That would depend on whether the extension needs a specific
>> interface or not.
>>
>> To transfer passwords, you need to copy key3.db and logins.json.
>>
>> For cookies, you need cookies.sqlite.
>>
>> You could simply copy the chrome directory into the new profile for
>> userContent.css.
>
> For me, I usually skip all this, redo them from scratch, etc. since I
> only care about my places.sqlite. Everything else can be recovered.

Thanks for all the replies!,

The reason why I wanted to avoid doing things by hand or from scratch is
that it's not just one, but five separate profiles.

Today I tried to do the migration by moving the profile directories and
it worked. There are some settings I still have to set or tweak, but
other than that, so far everything seems to show up in Seamonkey:
passwords, cookies, history, even some extensions.

And it feels faster than Firefox.

-- 
Nuno Silva
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-28 Thread Frank-Rainer Grahl
2.49.x will probably work with a 55 places database. Everything higher will 
fail. 52 should be ok but ymmv.


FRG


Nuno Silva wrote:

On 2018-11-27, Frank-Rainer Grahl wrote:


2.53 has the Firefox Library ported and should be compatible with at
least 58. 2.49.x has an older version. But I agree. Just use a
bookmarks export and redo the profile.

FRG


With which Firefox versions would 2.49.x be compatible? Some of the
Firefox profiles are from Firefox 52.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-28 Thread Don Spam's Reckless Son

Nuno Silva wrote:

On 2018-11-27, Frank-Rainer Grahl wrote:


2.53 has the Firefox Library ported and should be compatible with at
least 58. 2.49.x has an older version. But I agree. Just use a
bookmarks export and redo the profile.

FRG


With which Firefox versions would 2.49.x be compatible? Some of the
Firefox profiles are from Firefox 52.



Seamonkey 2.49.x can handle older profiles (within "reason")
Firefox 53 can also handle older profiles (ditto)
You should have no problems there.


--
spammus ergo sum
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-27 Thread Nuno Silva
On 2018-11-27, Frank-Rainer Grahl wrote:

> 2.53 has the Firefox Library ported and should be compatible with at
> least 58. 2.49.x has an older version. But I agree. Just use a
> bookmarks export and redo the profile.
>
> FRG

With which Firefox versions would 2.49.x be compatible? Some of the
Firefox profiles are from Firefox 52.

-- 
Nuno Silva
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-27 Thread Frank-Rainer Grahl
2.53 has the Firefox Library ported and should be compatible with at least 58. 
2.49.x has an older version. But I agree. Just use a bookmarks export and redo 
the profile.


FRG


Ant wrote:

On 11/27/2018 8:16 AM, EE wrote:

Nuno Silva wrote:

Hello,

Seamonkey Navigator has been my main web browser for more than a year
now, but I still have a few user profiles left in Firefox.

What would be the best way to move these profiles to Seamonkey? I would
like to preserve as much of the original profiles as possible,
including:

- History
- Bookmarks
- Preferences
- Installed extensions, if compatible
   (there are no webextensions)
- passwords and cookies
- userContent.css

Could/should I just move the profile directories to
$HOME/.mozilla/seamonkey and add them to profiles.ini?


(Is there some way I could then disable Mail only in these migrated
profiles?)

The file places.sqlite has history and bookmarks.  I have no idea if they 
are cross-compatible any more, however.  Bookmarks are easy enough to 
transfer.  Back them up or export as HTML and restore or import into SeaMonkey.


SM v2.49.4's old places.sqlite will work in the newer Firefox versions, but 
not in reversed. Firefox will upgrade it.



I imagine that some preference settings have changed, so comparing them by 
comparing prefs.js files or from about:config would be a good idea. Since 
SeaMonkey does newsgroups and email as well, there are a lot more preference 
settings for it.


If the extensions for Firefox were also written for SeaMonkey, there would 
be no problem, but I would check install.rdf in the .xpi files to make sure 
that they would be compatible with the target app (SeaMonkey) version.  If 
the extensions were not written for SeaMonkey, then running them through the 
converter website (http://addonconverter.fotokraina.com/) might be able to 
fix them.  That would depend on whether the extension needs a specific 
interface or not.


To transfer passwords, you need to copy key3.db and logins.json.

For cookies, you need cookies.sqlite.

You could simply copy the chrome directory into the new profile for 
userContent.css.


For me, I usually skip all this, redo them from scratch, etc. since I only 
care about my places.sqlite. Everything else can be recovered.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-27 Thread Ant via support-seamonkey

On 11/27/2018 8:16 AM, EE wrote:

Nuno Silva wrote:

Hello,

Seamonkey Navigator has been my main web browser for more than a year
now, but I still have a few user profiles left in Firefox.

What would be the best way to move these profiles to Seamonkey? I would
like to preserve as much of the original profiles as possible,
including:

- History
- Bookmarks
- Preferences
- Installed extensions, if compatible
   (there are no webextensions)
- passwords and cookies
- userContent.css

Could/should I just move the profile directories to
$HOME/.mozilla/seamonkey and add them to profiles.ini?


(Is there some way I could then disable Mail only in these migrated
profiles?)

The file places.sqlite has history and bookmarks.  I have no idea if 
they are cross-compatible any more, however.  Bookmarks are easy enough 
to transfer.  Back them up or export as HTML and restore or import into 
SeaMonkey.


SM v2.49.4's old places.sqlite will work in the newer Firefox versions, 
but not in reversed. Firefox will upgrade it.



I imagine that some preference settings have changed, so comparing them 
by comparing prefs.js files or from about:config would be a good idea. 
Since SeaMonkey does newsgroups and email as well, there are a lot more 
preference settings for it.


If the extensions for Firefox were also written for SeaMonkey, there 
would be no problem, but I would check install.rdf in the .xpi files to 
make sure that they would be compatible with the target app (SeaMonkey) 
version.  If the extensions were not written for SeaMonkey, then running 
them through the converter website 
(http://addonconverter.fotokraina.com/) might be able to fix them.  That 
would depend on whether the extension needs a specific interface or not.


To transfer passwords, you need to copy key3.db and logins.json.

For cookies, you need cookies.sqlite.

You could simply copy the chrome directory into the new profile for 
userContent.css.


For me, I usually skip all this, redo them from scratch, etc. since I 
only care about my places.sqlite. Everything else can be recovered.

--
"No, I'd prefer a cooler WITHOUT an ant-door, thank you..." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\If crediting, then use Ant nickname and URL/link.
  / /\ /\ \Axe ANT from its address if e-mailing privately.
 | |o   o| | http://antfarm.ma.cx / http://antfarm.home.dhs.org
\ _ /
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Migrating FF profiles to Seamonkey

2018-11-27 Thread EE

Nuno Silva wrote:

Hello,

Seamonkey Navigator has been my main web browser for more than a year
now, but I still have a few user profiles left in Firefox.

What would be the best way to move these profiles to Seamonkey? I would
like to preserve as much of the original profiles as possible,
including:

- History
- Bookmarks
- Preferences
- Installed extensions, if compatible
   (there are no webextensions)
- passwords and cookies
- userContent.css

Could/should I just move the profile directories to
$HOME/.mozilla/seamonkey and add them to profiles.ini?


(Is there some way I could then disable Mail only in these migrated
profiles?)

The file places.sqlite has history and bookmarks.  I have no idea if 
they are cross-compatible any more, however.  Bookmarks are easy enough 
to transfer.  Back them up or export as HTML and restore or import into 
SeaMonkey.


I imagine that some preference settings have changed, so comparing them 
by comparing prefs.js files or from about:config would be a good idea. 
Since SeaMonkey does newsgroups and email as well, there are a lot more 
preference settings for it.


If the extensions for Firefox were also written for SeaMonkey, there 
would be no problem, but I would check install.rdf in the .xpi files to 
make sure that they would be compatible with the target app (SeaMonkey) 
version.  If the extensions were not written for SeaMonkey, then running 
them through the converter website 
(http://addonconverter.fotokraina.com/) might be able to fix them.  That 
would depend on whether the extension needs a specific interface or not.


To transfer passwords, you need to copy key3.db and logins.json.

For cookies, you need cookies.sqlite.

You could simply copy the chrome directory into the new profile for 
userContent.css.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey