Good. There is maybe a lot of junk in permissions.sqlite. If you know what you
are doing you can clean it out with an sqlite editor like SQLiteStudio when
SeaMonkey is not running.
Also check the * global domain for junk.
You can also try the old cookie viewer to check the allowed cookie domains:
chrome://communicator/content/permissions/cookieViewer.xul
The Gecko migration utils in 2.39 and 2.40 actually double all older
permissions and add an http and https scheme. I have also seen ftp which
mostly doesn't make sense. I started over and deleted the permissions.sqlite
then. The broken Data Manager and cookie viewer were actually the reason I
started contributing to SeaMonkey :)
FRG
Jonathan N. Little wrote:
Jonathan N. Little wrote:
Well I selected "continue" on the two script warning dialogs and Data
Manager is up and working. I think I will selectively prune some stuff
that is not critical setting and see if that "fixes" the issue. I hate
so lose some of the setting that I do want to keep.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
