Closed
Bug 60528
Opened 24 years ago
Closed 16 years ago
Duplicate filters names in 4.x is broken in 6.0 - can't migrate filter with duplicate name
Categories
(Core Graveyard :: Profile: Migration, defect, P3)
Core Graveyard
Profile: Migration
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: gayatrib, Unassigned)
Details
4.x allows user to have duplicate filter names. When this profile is migrated to 6.0, only one filter is displayed. This is a problem and needs to be fixed. In 6.0, we do not allow the user to enter duplicate filter names. The fix for this is in bug 41851.
Comment 2•23 years ago
|
||
I'd say WONTFIX this. We can't accept duplicate filter names. Sorry.
Comment 3•23 years ago
|
||
no, you can't WONTFIX this - in 4.x you could create filters with duplicate names - at the very least we have to rename the duplicate names during profile migration (though at this point many people have already migrated their 4.x profile to mozilla, so they probably already have duplicate names)
Comment 4•23 years ago
|
||
Alecf: good point. so can we give this to the migration people or do we have to do the renaming work ourselves? :)
Updated•20 years ago
|
Product: MailNews → Core
Comment 6•17 years ago
|
||
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Updated•17 years ago
|
Severity: normal → minor
Component: MailNews: Filters → Profile: Migration
OS: Windows NT → All
QA Contact: laurel → profile-migration
Hardware: PC → All
Summary: Duplicate filters names in 4.x is broken in 6.0 → Duplicate filters names in 4.x is broken in 6.0 - can't migrate filter with duplicate name
Comment 7•16 years ago
|
||
Marking bugs related to migrating 4.x profiles as wontfix, as this is no longer supported. If this bug isn't specific to 4.x, please reopen it.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•