(Gloda) Open Message in Conversation breaks for Local Folders, if multiple messages moved or Archived from imap to local. Error "Couldn't find a collection for msg".
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
People
(Reporter: mozdev2, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: dataloss, testcase)
Attachments
(1 file, 1 obsolete file)
|
4.18 MB,
image/gif
|
Details |
Comment 1•10 years ago
|
||
Updated•10 years ago
|
Comment 6•10 years ago
|
||
Comment 7•10 years ago
|
||
| Reporter | ||
Comment 10•10 years ago
|
||
Comment 11•10 years ago
|
||
Comment 12•10 years ago
|
||
| Reporter | ||
Comment 13•9 years ago
|
||
Comment 14•9 years ago
|
||
| Reporter | ||
Comment 15•9 years ago
|
||
| Reporter | ||
Comment 16•8 years ago
|
||
| Reporter | ||
Comment 17•7 years ago
|
||
This bug is still present in 60.2.1. Seems serious? Anyone have a sec to check it out? Thanks!
Comment 18•7 years ago
|
||
Still present in 60.8.0 and this bug is much wider than just Local Folders. If you move your entire Inbox/Sent folders to Archive, "open message in conversation" stops working inside archive completely. Very painful if the archive contains k's of emails.
Error message in the console:
Couldn't find a collection for msg: [xpconnect wrapped nsIMsgDBHdr] msgHdrViewOverlay.js:2894
Comment 19•7 years ago
|
||
Very well described by CC, and thanks Dorphus for confirming. I can also confirm.
This goes back to bug 641446, and others listed in query [1] like Bug 989884 - Gloda index error "Problem encountered during message move/copy: undefined" when move more than one messages to local folder. If "outdated msf condition" exists Gloda should take some action or wait for recovery (rebuild/repair-index)
Updated•2 years ago
|
Description
•