Closed Bug 19013 Opened 20 years ago Closed 11 years ago

Migration carries forward unsubscribed category groups.

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: laurel, Unassigned)

References

Details

After migrating a 4.x profile which unsubscribed a categorized newsgroup, the
5.0 profile will still show at least the root category/group of the categorized
group structure.

Note: I know there may be many combinations of unsubscribing within the
categorized group structure, but I've tested only the simple case of
unsubscribing the root/whole category group structure.

Steps to reproduce:

1.  Launch 4.x to messenger.
2.  Add news server zia (default regular port 119).
    Through the Subscribe dialog (File|Subscribe) subbscribe to group "flowers"
or "laurel" and confirm OK from the subscribe dialog.
3.  Note the server and categorized group hierarchy appears in the folder pane.
4.  Select the root group/category and Edit|Unsubscribe. Confirm OK to the
confirmation dialog which appears.  The group is removed from the 4.x display.
    Note:  depending on whether you Unsubscribe the collapsed hierarchy or just
select the root category group from an expanded group hierarchy will determine
how much of the category group structure will be carried forward into 5.0. If
you unsubscribe the collapsed group, you'll see the whole group hierarchy in 5.0
and if you unsubscribe just the root category while expanded you'll just get the
root category/group in 5.0.
5.  Migrate the profile to 5.0 and go to messenger. Open the news server zia.
    Notice the unsubscribed group(s) still appear.

Actual result: unsubscribed group(s) carried forward to 5.0.

Expected result:  the group should not apper in the 5.0 folder pane.

Found using Nov15-21 m11 commercial builds on NT 4.0 and Linux 6.0.
QA Contact: gbush → laurel
Status: NEW → ASSIGNED
Target Milestone: M13
marking m13, accepting.
Target Milestone: M13 → M15
moving this bug to m15

the bad news:

1)  we aren't parsing / using hostinfo.dat yet.
2)  we aren't dealing support / dealing with categories yet.

the good news:

hostinfo.dat gets migrated correctly for all three platforms, so we can live
with how things are for now.  once we add category and hostinfo.dat support back
in, we will be fine.
moving to m16.
Target Milestone: M15 → M16
Is this feature work?  Is it time-consuming, critical to the product, or risky 
to do later?  If none of the above, we should move this out of M16.  Seth, 
please make the call.
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
Component: Profile Migration → Subscribe
these are all subscribe bugs.   accepting.
Seth, when I verified bug 39763, I saw this problem. 
Should this bug nominate for nsbeta2?
How bad is this and is there anything we can do to fix this if we aren't
supporting categories?
Keywords: nsbeta3
Target Milestone: M17 → M18
Well, when the category groups appear in seamonkey, they are all separate
groups. So, if you happen to have unsubscribed to a category in 4.x which was
part of a large category group tree, you'll get the whole category group tree
back in seamonkey as N separate groups and you have to unsubscribe individually
to all of them (or perhaps delete the account and start it over again).  I'm
assuming the unsubscribe will hold.
the number of people this will affect is miniscule. I doubt we'll ever bother to 
fix this.
I feel so miniscule. :)
If that's the case (not Laurel feeling miniscule but David's comments about 
fixing this :-) ) then I'm going to move to the future milestone and remove the 
nsbeta3 nomination.
Keywords: nsbeta3
Target Milestone: M18 → Future
Poor Laurel - David, stop picking on her :-)
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: laurel → search
Priority: P3 → --
Target Milestone: Future → ---
This bug is being marked EXPIRED as it has seen no activity in a very long time.

If you think that the issue reported might still be relevant, please test with a recent release of SeaMonkey and if the problem persists feel free to re-open the report. Thank you.

http://www.seamonkey-project.org/
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → EXPIRED
This bug is being marked EXPIRED as it has seen no activity in a very long time.

If you think that the issue reported might still be relevant, please test with a recent release of SeaMonkey and if the problem persists feel free to re-open the report. Thank you.

http://www.seamonkey-project.org/
Bulk reopening incorrectly expired bugs - no activity does not constitute no bug - these need proper checking.
Status: RESOLVED → REOPENED
Resolution: EXPIRED → ---
4.x migration is dead, let's make this bug go away.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.