Closed Bug 6614 Opened 25 years ago Closed 25 years ago

Profile Creator not writing specified prefs to Prefs50.js

Categories

(Core Graveyard :: Profile: BackEnd, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: bmartin, Assigned: racham)

References

Details

Latest Profile Creator

1. Launch Apprunner on clean system (delete Users50\, delete
Windows\mozregistry.dat prior to running apprunner.exe)
2. Proceed through the Profile Creator screens and input data in each text field
3. Select the "Finish" button on the last screen.
4. go to the Users50\ directory, open the new profile's folder and open the
associated prefs50.js file in Notepad.

Results:

The user specified preferences are not getting set in the prefs50.js file by the
Profile Creator.
Status: NEW → ASSIGNED
Target Milestone: M7
This will be fixed real soon.
*** Bug 7564 has been marked as a duplicate of this bug. ***
Changes have been proposed to change the profile wizard UI.
All the mailnews preferences will be collected via Mail Account Wizard.
In fact we can turn off all those screens in the wake of above
change and move the target milestone M8.
Target Milestone: M7 → M8
Current Wizard app has just 1 screen to collect minimal information. Other
information will be collected based on the new UI which is scheduled to M8.
Moving TFV to M8.
*** Bug 8176 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Not collecting any mail/news info. MailNews account wizard will be doing that.
Profile wizard now has only one page that collects the information from the user
and all that information is stored in the registry. Marking this bug invalid.
gbush...if all is cool with you, please mark Invalid
Status: RESOLVED → VERIFIED
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.