Preferences directory should be settable outside of windows directory

RESOLVED INCOMPLETE

Status

Core Graveyard
Profile: BackEnd
--
enhancement
RESOLVED INCOMPLETE
17 years ago
2 years ago

People

(Reporter: Martin Petricek, Assigned: Conrad Carlen (not reading bugmail))

Tracking

Trunk
Future
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
Mozilla tries to write user profiles under c:\win95\Mozilla
But since the directory is write-protected, it will fail and
it won't be able to write the profile. Mozilla doesn't even protest,
that the  diractory couldn't be created, it just silently don't write
the profile and I have all reset to default when I start mozilla again.
I have win98 SE here.

On another computer in school there is windows directory set to ramdisk,
and if the computer crashes, any changes to preferences, cookies, etc...
are gone since the the profile is on ramdisk and I won't manage
to save it back to network disk when staring at "blue screen of death, press
reset to continue".

There should be some option to set profiles direcory to somewhere else.
Older mozilla versions used users50 direcotory in root of the drive where
mozilla is installed, which happen to be here e:\users50 and m:\users50 in 
school
and it's writeable.

I think ideal solution will be some small .ini file or other plaintext
configuration file in directory with mozilla.exe binary that will say where to
look for user profiles directory (the default may be $windir for windows
and $HOME for unixes)

Comment 1

17 years ago
imo this bug is invalid:
mozilla -createprofile Name "c:\path" should work iirc
so would
mozilla -profilemanager
click create profile and browse for a path..

the only question is what about mozreg.dat or whatever.
Assignee: asa → ccarlen
Component: Browser-General → Profile Manager BackEnd
QA Contact: doronr → gbush
(Assignee)

Comment 2

17 years ago
Yeah, the registry would still be a problem.

> I think ideal solution will be some small .ini file

There's several ways to go about it.  
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → mozilla1.0
(Reporter)

Comment 3

17 years ago
Well, I can set the prefs directory to e:\users50\default where it was before,
but since mozilla is also unable to create the registry file, it won't even try
to load the profile from there when started again. (i suppose the path to
profile directory is stored there)
Another small problem is that when I pick the e:\users50\default as a profile
directory, it will create some subdirectory with some cryptic name like
"rkml4a28.slt" and put all the profile data into it, instead of the chosen
directory.
(Assignee)

Comment 4

17 years ago
> (i suppose the path to profile directory is stored there)
That's right.

> it will create some subdirectory with some cryptic name like "rkml4a28.slt"
That's by design (for security) and is not going to change. If you want to know
the whole (long) story on that, see bug 56002.


Comment 5

17 years ago
changing QA contact
QA Contact: gbush → ktrina

Comment 6

17 years ago
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
(Assignee)

Comment 7

16 years ago
Setting to milestone that's not passed.
Severity: major → enhancement
Target Milestone: mozilla1.0.1 → Future
What's the position on this now? How does mozilla know where to look for 
registry.dat and can the location where mozilla stores this file be changed? 
QA Contact: ktrina → profile-manager-backend

Updated

5 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.