Bug 310633

Summary:	Poor error message when trying to create a folder that already exists
Product:	[Applications] kmail2	Reporter:	Bernd Oliver Sünderhauf <pancho.s>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	wishlist	CC:	montel
Priority:	NOR
Version:	4.9.3
Target Milestone:	---
Platform:	Chakra
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bernd Oliver Sünderhauf 2012-11-25 02:01:08 UTC

When trying to create a folder that already exists, the following error message is displayed:
"Could not create folder: Could not create collection foo resourceId: 12"

This is not always that obvious as kmail might not be subscribing the folder, so there should be an indication that a folder with this name already exists.
"Could not create folder 'foo' because it already exists in [name of resource/folder]. " => OK

Ideally the user is informed of that fact that the folder is not displayed because it is not subscribed, so the error message would ask something like:
"Could not create folder 'foo' because it already exists in [name of resource/folder]. Do you want to subscribe this folder?" => [Yes] / [No]

After clicking [OK] In the first case, or [No] in the second case, the input dialog underneath the error message shouldn't be closed, so the user can try again rightaway.
When clicking [Yes] in the second case, the "Manage local subscriptions" dialog should be opened instead, marking the line with the concerned folder.

Reproducible: Always

Comment 1 Laurent Montel 2012-11-26 08:13:16 UTC

You unsubscripted a folder and after try to create it ?

Comment 2 Bernd Oliver Sünderhauf 2012-11-26 09:09:46 UTC

No, actually I hit Bug #305269, hiding created top-level IMAP folders.
Might be true that the case "recreate folder after unsubscribing" is too edgy to receive special attention. However, this was only described as a scenario where it is even less obvious that a folder already exists.

So if we leave out the "Ideally..." section of my proposal, the minimum remaining is:
Akonadis failure to create a folder which (for whatever reason) already exists on the server, shouldn't lead to a cryptic error such as: "Could not create folder: Could not create collection foo resourceId: 12".
What I'm asking for is a more meaningful and understandable error, such as:
"Could not create folder 'foo' because it already exists in [name of resource/folder]. " => OK

Akonadi's error could possibly be caught be kmail. However, this might be Akonadi's job, because Akonadi knows better why the folder couldn't be created.

Comment 3 Bernd Oliver Sünderhauf 2012-11-26 09:12:59 UTC

Should I move this one to the Akonadi queue?

Comment 4 Bernd Oliver Sünderhauf 2012-11-29 08:24:34 UTC

Removed extramile tag: Doesn't regularly affect many people, rather an edge case.