Please report any other irregularities here.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 SeaMonkey/2.0a3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 SeaMonkey/2.0a3 Sea Monkey Beta 2 -- Password Manager does not work on any of my bank pages or other secure sites, like credit cards, Amazon, etc. Also does not work consistently on other sites. Reproducible: Always Steps to Reproduce: 1. Go to a secure site and log in 2. 3. Actual Results: Nothing Expected Results: Expect Password Manager to ask if password should be saved.
(Q1) Do you use migrated profile from profile of Sm 1.1.x by Seamonkey 2 Beta? (Q2) If yes for Q1, multiple fields were saved in SignonFile of Sm 1.x? Check prefs.js setting of signon.SignonFileName, and check the ????????.s file content in profile directory of Sm 1.x. (Q3) If yes for Q1, do you share the migrated profile with Seamonkey 1.1.x? Check ...\profile.ini content. IsRelative=1 and Profiles/<profile_directrory_name> ? The profile directory used by Seamonkey 2 Beta is same one for Sm 1?
I'm sorry, but I have no idea what your comments mean.
If migrated, password manager's entry already exists, then no asking for "save password or not" is very normal behavior. And if migrated, multiple field's data in passward manager's file possibly causes issue due to password manager's spec change; - Password manager of Sm 1 : Supports multiple filed's data - Password manager of Sm 2 : AFAIR, Sm 2 supports single filed only (password + one username filed. Same as Firefox) > Expected Results: > Expect Password Manager to ask if password should be saved. Can you reproduce problem with newly created profile?
Thanks for staying on this with me, WADA, but the problem is that while I am an experienced computer user, I'm not so good working "under the hood." I think I did migrate from SM 1 to 2, although I think I uninstalled SM 1 first. I probably did not delete all the files associated with SM1. Is there a file (in SM2) that I can delete or edit to start all over with Password Manager? I only have 3-4 memorized, so deleting is not a problem. This would be the simplest solution for me. Thanks.
Profile location was changed by Sm 2. Sm 1: "%appdata%Mozilla\registry.dat" (binary file) => "%appdata%Mozilla\Profiles\<profile_dir>" Sm 2: "%appdata%Mozilla\Seamonkey\profile.ini" (text file) => "%appdata%Mozilla\Seamonkey\Profiles\<profile_dir>" (or => "%appdata%Mozilla\Profiles\<profile_dir>" : profile is used by Sm 1 Type next commands at Command Prompt. > DIR "%appdata%\Mozilla" > DIR "%appdata%\Mozilla\Profiles" /A D > DIR "%appdata%\Mozilla\Seamonkey" > DIR "%appdata%\Mozilla\Seamonkey\Profiles" /A D Before touch your daily use profile, create new profile and test with it first. Start Sm 2 by "seamonkey.exe -P" => Profile manager is invoked. And check profiles.ini content and all prefs.js content. Question again: Is your problem reproduced with newly created profile by Sm 2?
I have not been able to solve this "problem," and I am beginning to wonder if it is a Sea Monkey problem after all. Here's why: I started using a SM add-on called Last Pass, which is a password manager. Although I have passwords and ID names for some of the secure sites for which SM did not work (I got the passwords by importing them from Roboform, which I was using in Firefox), Last Pass reported it couldn't find any matching fields for my user ID or password. So I have concluded that there may be a problem with some secure sites, some incompatability with SeaMonkey that is accounting for the fact that the Password Manager doesn't prompt to save a new password and user ID at these sites. I will continue to use Last Pass, although it lacks an important feature: generating passwords. It has this feature in a version for FireFox, but not for Sea Monkey. Thanks for your help. David
Closing as INCOMPLETE for the time being. If you some new specific information please reopen.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.