Closed Bug 32934 Opened 25 years ago Closed 25 years ago

Profile Migration Confirmation Dialog says "5.0"

Categories

(SeaMonkey :: Startup & Profiles, defect, P3)

Product:
SeaMonkey
Component:
Startup & Profiles
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: kevinyen, Assigned: bugs)

References

Details

(Keywords: polish, Whiteboard: [nsbeta2-][PDT-] [nsbeta3+])

The confirmation dialog that arises when I choose to migrate a profile includes the sentence: "Netscape can copy your 4.x profile to use for 5.0". Should say 6 or Netscape 6. thx, kevin
Keywords: beta1
Target Milestone: ---
Putting on the PDT- radar for beta.
Whiteboard: [PDT-]
Ben, got this one fixed to. see me on irc tonight so you can review
fixed for mozilla, ben you need to change in the commercial tree
Let's do this for beta 2 obviously ...
Target Milestone: --- → M16
*** Bug 35304 has been marked as a duplicate of this bug. ***
*** Bug 35540 has been marked as a duplicate of this bug. ***
Copied from bug 35540: The "Confirm" dialog states: "The profile you have selected was created with a previous version of Communicator and must be converted before you can use it with Netscape. Netscape can copy your 4.x profile to use for 5.0. Your original 4.x profile will not be altered. Choose OK to convert the profile, or Cancel to return to the Profile Manager and select another." Please change to: "The profile you selected was created using a previous version of Netscape. It must be copied and converted for use with Netscape 6. You original 4.x profile will not be altered. Choose OK to copy and convert the profile, to Cancel to return to the Profile Manager and select another profile." Biggest change: delete reference to 5.0. However, please note other changes that reduce the number of words and clean up the text a little bit.
Keywords: nsbeta2
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [PDT-] → [nsbeta2+][PDT-]
I think I fixed this.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
not fixed in build 2000-05-16-09M16 for Win32
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Move to M18.
Target Milestone: M16 → M18
fixed
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
alas- Mozilla is used in the commercial version- as in '...before you can use with Mozilla.' Should be Netscape 6
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Per todays PDT Nav Beta 2 review, moving to [nsbeta2-].
Whiteboard: [nsbeta2+][PDT-] → [nsbeta2-][PDT-]
Keywords: polish
Whiteboard: [nsbeta2-][PDT-] → [nsbeta2-][PDT-] [b3nav+]
nav triage team: [b3nav+] now = [nsbeta3+]
Whiteboard: [nsbeta2-][PDT-] [b3nav+] → [nsbeta2-][PDT-] [nsbeta3+]
The problem originally described in this bug has been fixed (5.0 references). I've modified 42869 which deals with a similar thing to what Grace reports (and in fact the fix for that is exactly the same to the fix for the problem she reports here) - 42869 now refers to all "Mozilla in Netscape" text issues for the Profile manager (which number about 3). Resolving this one as fixed.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
verified in build 2000073121M18
Status: RESOLVED → VERIFIED
Adding keyword to bugs with nsbeta3 triage value in status whiteboard so tracking queries will not be misled
Keywords: nsbeta3
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.