Bug 240723 - We can not exclude tags folder or search folder from AkonadiCombobox or CollectionDialog
Summary: We can not exclude tags folder or search folder from AkonadiCombobox or Colle...
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: libakonadi (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: LO normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: akonadi-ports-regression, investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-06-04 14:49 UTC by Laurent Montel
Modified: 2018-10-21 04:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laurent Montel 2010-06-04 14:49:44 UTC
Version:           unspecified (using Devel) 
OS:                Linux

When we use AkonadiCombobox or collectionDialog sometime it's necessary to exclude Search Folder or tag folder.
But it's not possible still

Reproducible: Didn't try

Steps to Reproduce:
Create a search in kmail so you can see search folder.
After that open composer and combobox and you can see search folder.

Actual Results:  
We show search folder :)

Expected Results:  
I want to have a function to exclude it
Comment 1 Tobias Koenig 2010-08-02 21:27:50 UTC
Hej,

this should be handled by the access right iirc. So virtual collections are normally not writable, so they won't show up in the 'Select save collection' dialog anyway. Or do you have another use-case in mind?

Ciao,
Tobias
Comment 2 Laurent Montel 2010-08-03 10:42:46 UTC
Virtual folder is not read only :)
"Search Folder" top level is read-only but sub-folder is read-write.
=> it creates a problem

because we can specify it as a folder for pop3 resource (destination folder)
or add a contact in this directory in kaddressbook etc.

So for the moment it's not good.

I didn't test with tag account but perhaps the same pb.
Comment 3 Andrew Crouthamel 2018-09-20 22:08:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:52:38 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!