Open Bug 515021 Opened 15 years ago Updated 2 years ago

Cannot rename virtual Search Folder under News server account

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86_64
Windows 7
defect

Tracking

(blocking-thunderbird3.1 -, thunderbird3.1 wanted)

ASSIGNED
Tracking Status
blocking-thunderbird3.1 --- -
thunderbird3.1 --- wanted

People

(Reporter: jesse.houwing, Assigned: aceman)

References

Details

Attachments

(3 files)

I created a virtual Search folder under my news group account. This search is shown at the bottom of the folder tree. I'd like it to be on top. I tried renaming the folder, but the Rename option does not accept any proposed value.

Steps to reproduce:
- Click on the news server
- Hit ctrl-shift-f
- create a search and save as search folder (choose the newsserver as parent)
- Notice that the search foler appears on the top of the list (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=506520)
- restart thunderbird
- right-click the Search Folder and choose rename
- enter any value
- click Rename

Expected:
- Folder is renamed or an error message is shown telling me why my proposed name was rejected

Actual result:
- Nothing happens.
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIMsgFolder.rename]"  nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame :: chrome://messenger/content/folderPane.js :: renameCallback :: line 1743"  data: no]
Flags: blocking-thunderbird3.1?
not blocking, but wanted. There are a whole host of bugs having to do with saved searches under news folders, having to do with the fact that we're paying attention to news folder capabilities which don't apply to saved searches (e.g., rename).
blocking-thunderbird3.1: --- → -
Flags: blocking-thunderbird3.1?
Attached patch patchSplinter Review
Assignee: nobody → acelists
Status: NEW → ASSIGNED
Attachment #715774 - Flags: review?(Pidgeot18)
Comment on attachment 715774 [details] [diff] [review]
patch

Review of attachment 715774 [details] [diff] [review]:
-----------------------------------------------------------------

Pursuant to the comments in bug 272490, I don't think this is desirable right now.
Attachment #715774 - Flags: review?(Pidgeot18) → review-
See Also: → 272490
So would you accept a patch that hides the Rename item in the context menu while it is not working?
Attachment #8362718 - Flags: review?(mkmelin+mozilla)
Attachment #8362718 - Flags: review?(Pidgeot18)
Comment on attachment 8362718 [details] [diff] [review]
patch - hide Rename option

Review of attachment 8362718 [details] [diff] [review]:
-----------------------------------------------------------------

I suppose, but do add a comment about why. 
Personally, I'd prefer to go with the earlier patch though. From an end user perspective that's what we want, and in the end that's all that matters.
Attachment #8362718 - Flags: review?(mkmelin+mozilla) → review+
Yeah, I would like it too, but it didn't pass through jcranmer.
Comment on attachment 8362718 [details] [diff] [review]
patch - hide Rename option

Review of attachment 8362718 [details] [diff] [review]:
-----------------------------------------------------------------

I know I've been avoiding this patch for a while.

I think you misunderstood the direction I wanted to drag virtual folders and NNTP in: this is only making it worse (although subtly so).

The main problem is that I don't want nsMsgNewsFolder--or nsIMsgNewsFolder in IDL terms--to implement a virtual folder. The obvious solution to this conundrum is to divorce the definition of a newsgroup based not on folder.server.type but rather on folder instanceof (or, better yet, folder capabilities instead of instanceof checks). I do realize it's not idiomatic, but I think lives would be easier if we started making it so.
Attachment #8362718 - Flags: review?(Pidgeot18) → review-
(And, fwiw, a more useful use of time would be not trying to patch over failures but figuring out how to make NNTP servers not use nsMsgNewsFolder for implementations of virtual folders rather than trying to patch individual pain points).
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: