Closed
Bug 57830
Opened 25 years ago
Closed 25 years ago
Profile Migration causes wrong default Sidebar tab
Categories
(Core Graveyard :: Profile: Migration, defect, P1)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: johng, Assigned: paulkchen)
Details
(Whiteboard: [rtm need info])
Attachments
(1 file)
|
1.76 KB,
patch
|
Details | Diff | Splinter Review |
When you migrate a 4.x profile, the default list of Sidebar tabs does not
correctly choose the right tab to be default.
win95 build from 10/23
For example, on Netscape commercial builds, the default list (as detailed at the
beginning of bugscape bug 2847) calls for the News tab to be open by default.
However, the last tab, the Today's Tips tab (earlier know as Sidebar Today) is
incorrectly open by default.
We need urgent QA help to define exactly what happens and when on the various
platforms. cc'ing shrir who is the Sidebar QA lead and assigning the bug to
profile migration so their engineer and QA lead can look at this, too.
keyword rtm
This has a huge impact on our traffic forecasts and business model. Depending
on exactly when the user runs into this bug, this could be a pull off the wire
thing.
Keywords: rtm
Actually, I just found out that for the windows build, the install is using the
wrong localstore.rdf. My windows commercial branch build contains the correct
localstore.rdf. I would guess somehow installer is using the wrong one.
Comment 3•25 years ago
|
||
dbragg is out today, so if you're looking for immediate action you may want to
assign to someone else. hard to see how migration could be the culprit since
this file is not migrated.
How could the install be using the "wrong" localstore.rdf? This file is
identical between mozilla and ns.
dveditz, not anymore. I had split them to make the default tab change for
commercial only. Wouldn't want mozilla localstore.rdf to reference a panel only
availble in a commercial build now, would we?
Comment 5•25 years ago
|
||
A ha! found a culprit to pin this on -- reassigning. When you change files that
should get delivered you need to update the package lists.
In this case the three ns/xpinstall/packager/packages-<foo> files need to have
the localstore.rdf file added to the [deflenus] section to overwrite the
corresponding one copied from the Mozilla build and packages-<foo> lists.
At least, this is enough of a safe fix to be checked into the RTM branch. In
addition it looks like profile migration pulls files directly from
defaults/profile rather than defaults/profile/<locale>. That part of the bug
should be fixed on the trunk and be assigned to Tao. Maybe we need a separate
bug for that case.
Assignee: dbragg → pchen
Comments:
1. Regarding the maintenance of packager-*, module owners is responsible of
adding new files to langenus or deflenus.
2. In migrating a profile (especially from 4.x), defaults/profile/* is
used since profile locale info might not be available yet. This is
especially true in migrating 4.x profile.
Comment 8•25 years ago
|
||
adding dbragg and sspitzer to the CC, masters of the profile migration process.
johng: would you consider this a stop ship? I'm just trying to get this on the
radar of PDT early.
Comment 10•25 years ago
|
||
Comment 11•25 years ago
|
||
Without this patch (which simply explicitly adds the *commercial*
localstore.rdf to the *commercial* deflenus.xpi -- this should be a bugscape
bug) we ship the Mozilla version of localstore.rdf instead of the branded one.
Comment 12•25 years ago
|
||
r=tao for (dveditz's patch:
http://bugzilla.mozilla.org/showattachment.cgi?attach_id=17965)
low risk; high reward.
| Assignee | ||
Comment 13•25 years ago
|
||
I've created bugscape 3042 for this bug because it's really an ns installer problem.
| Assignee | ||
Comment 14•25 years ago
|
||
Resolving invalid because the bug is really an installer problem, also have
logged bugscape 3042 as the new form of this bug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Comment 15•25 years ago
|
||
This bug is not invalid because you forgot to update the install package lists
when you created a new file, it's invalid because it's a commercial problem not
a Mozilla problem.
| Assignee | ||
Comment 16•25 years ago
|
||
Ok, ok, uncle. dveditz is correct, what I should of said was that this bug is
invalid because it is a commercial installer issue.
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
•