Closed
Bug 14908
Opened 25 years ago
Closed 25 years ago
[DOGFOOD]Copy 5.x defaults into profile before migrating old content
Categories
(Core Graveyard :: Profile: BackEnd, defect, P3)
Core Graveyard
Profile: BackEnd
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: selmer, Assigned: racham)
References
Details
(Whiteboard: [PDT-])
There are some new files that need to be in a profile for the app to work properly. We currently don't attempt to make sure these files exist in migrated profiles because we assume all the content should come from the original profile. There are soon to be some rdf files and other stuff that should be in all profiles - even migrated profiles. If we make this part of our existing defaults directory handling, then we should be able to support this with very little effort. By copying the files into the directory and then doing migration, we make sure the new stuff exists and we also give the old stuff a chance to override it. An example would be the bookmarks.html file that gets overridden by the migrated copy of that file and a new rdf file that wouldn't ever exist in an old profile would properly make its way into the 5.x version of that profile. I think this change can be isolated within the profile manager rather than pushing it down into the migrator. In essence, the profile manager will create the new profile container and fill it with defaults and then let the migrator fill it up with the migrated content. Check with Waterson about how this will be used.
Whenever we create an equivalent folder (to 4.x profile) under Users50, we can use RecursiveCopy routine to copy the contents from the 'defaults' folder. The location os 'default' folder must be obtanied using the file locator service.
Reporter | ||
Updated•25 years ago
|
Summary: Copy 5.x defaults into profile before migrating old content → [DOGFOOD]Copy 5.x defaults into profile before migrating old content
We don't quite understand why this prevents someone from using dogfood. The bug is not very clear as to the problem. Is there data loss? If so, please resubmit
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking this Fixed. A fix has been checked to copy the required 5.0 default profile files into the migrated file. For future reference, Bug 24294 will be the bug that will do this using nsLocalFileSpec* implementation.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 7•25 years ago
|
||
verified on build 2000011808 using windiff to view 5.0 only files copied to migrated files
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•