Stanimir Stamenkov wrote:
Mon, 15 Aug 2011 16:44:32 -0400, /PhillipJones/:
Stanimir Stamenkov wrote:
Now to the exact problem you're experiencing, I hope you've read the
release notes (the Known Issues) for 2.1, 2.2 and 2.3 versions:
http://www.seamonkey-project.org/releases/seamonkey2.1/#issues
http://www.seamonkey-project.org/releases/seamonkey2.2/#issues
http://www.seamonkey-project.org/releases/seamonkey2.3/#issues
All of these state:
* Data loss warning: If you use a profile with this or any later version
and then try to go back to SeaMonkey 2.0, SeaMonkey will rename your
history file to places.sqlite.corrupt and create a new places.sqlite
file, effectively resetting your browsing history. This is because the
internal format changed and the upgrade process only works in one
direction.
In any case you go back using your profile with SeaMonkey 2.0, even for
just one session, you'll find your bookmarks gone starting with
SeaMonkey 2.1 and subsequent versions, next.
Yes I Understand and I do have. else I would not be using my 2.0.14 now.
From my understanding of what I have been reading, the developers have
no idea how to fix this problem of not converting bookmarks and it can
strike anytime with no warning.
This should be the top number one bug to be fixed.
Honestly I don't understand which part of "the upgrade process only
works in one direction" you don't understand. May be you think you're
smarter than the developers which have given you exact instructions on
what _not_ to do, but you've done it anyway... and then you've been
given number of advises how to recover from your mistake. I don't think
the SeaMonkey developers could invest more just to make an automatic fix
for your mistake. If it was that easy, they would have done it already.
Look if you have hundreds of Bookmarks and the disappear. when you
switch to updated browser. Wouldn't you want the bug fixed.
You don't understand this a Deal Breaker! No one is going to update to
something That wipes out years of Bookmarks/Links you've built up. Up
until 2.3 this wasn't a major problem.
No I am no developer. And I don't know the intricacies bug fixing. You
developers say say you want users to tell you what bugs are happening
Yet when you get told, Its you don't know this, you don't know that. So
either you want it.
This is almost as bad, as SM Crashing the instance you open.
--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net mailto:pjon...@kimbanet.com
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
