Create profile needs to copy contents from Defaults folder

VERIFIED FIXED in M8

Status

Core Graveyard
Profile: BackEnd
P3
normal
VERIFIED FIXED
19 years ago
2 years ago

People

(Reporter: selmer (gone), Assigned: racham)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
For parity with 4.x, the profile creator must copy the contents from the
application's Defaults folder into every new profile.
(Reporter)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M8

Updated

19 years ago
Blocks: 7921

Comment 1

19 years ago
So what's the status on this bug? Will it be fixed for M8? I am trying to get
7921 done.

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 2

19 years ago
Checked in the code to support the above. Here is the list of locations for the
defaults folder on the different platforms.

Win : \dist\ProfileDefaults
Mac : :Documents:Mozilla:ProfileDefaults
Unix : ~/.mozilla/ProfileDefaults
BeOS : mozilla/ProfileDefaults
(Reporter)

Updated

19 years ago
Status: RESOLVED → REOPENED
(Reporter)

Comment 3

19 years ago
Is there a compelling reason why we're not using the same defaults folder we've
used in every previous release?
(Assignee)

Comment 4

19 years ago
The only reason (for not using name Defaults) is that the name Defaults is very
close the folder name Default which gets created when user chooses to create
profile named "default", i.e., a case where user does not override the default
profiole name "default". Though on Windows and Mac the Defaults (i.e.,
ProfileDefaults) folder lives one level above the profile directories, on Unx
and BeOS, the directory lives along with the profile directories. So to avoid
confusion (while maintaining the same name across all platforms), name
ProfileDefaults is picked.

Updated

19 years ago
Resolution: FIXED → ---

Comment 5

19 years ago
Clearing Fixed resolution since this has been Re-opened.

Comment 6

19 years ago
I can see the ProfileDefaults folder being created - but no information is being
stored-what should go there? data saved between builds? bookmarks--per 7921?
(Reporter)

Comment 7

19 years ago
After talking to Bhuvan, it appears that the conflict with the name "Defaults"
is from the concept of putting this folder in with the profiles of a particular
user on Unix machines.  This concept is incorrect.  The Defaults folder is a
mechanism for distributors to change the default content of newly created
profiles and is not tied to a particular user as suggested.  In any case, where
would the content in the user directory come from?

For this to work properly, the Defaults folder needs to be created and filled by
the installer and then copied into every new profile as it's created by the
app.  For our internal usage, it's OK to check in a Defaults folder that lives
in the dist with the executable and put content in it to help people test
things.  This should probably live in the mozilla/profile directory in CVS and
it should have a makefile to move everything into the right place in the dist.
(Assignee)

Updated

19 years ago
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 8

19 years ago
A directory named "defaults" is added to mozilla/profile. All the defaults files
that need to go into the directory of newly created profile live under this
folder. At present, only bookmarks.html exists in that folder. Makefiles in that
folder should be updated whenever a new file is added to that ("defaults")
directory. In the build process, files in the "defaults" folder gets copied to
the following destinations on different platforms.

Windows : <install directory>/defaults
Unix    : <install directory>/defaults
Mac     : <install directory>:Defaults

When a new profile is created, all the files in the above folder gets copied
into that profile directory.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Updated

18 years ago
Component: Profile Manager → Profile Manager BackEnd

Comment 10

18 years ago
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.