-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add own categories, delete default ones #1644
Comments
You can add own categories in 2.0.1 (and probably also in some earlier versions). Deleting the defaults seems to not be possible at the moment, self-created categories don't show up in the list. Also see #71 |
You miss understood me or I wasn't specific enough. Adding a own Category to one event works but also assigning this category to an other event needs to be done manually (I talk about the Web Interface). When multiply users have access to this Calendar, this would be an issue. My idea is that an admin can add own categories that should be used as default and others not. When everyone needs to retype a category, small differences can occur and would mess things up. For a single user, this won't be an issue, because in Thunderbird I can add my own categories and just using them but this isn't possible for the web client. |
So in addition to what is available now:
I could also imagine the Flow-App to integrate with this somehow, also kind of related to #1540 (Comment) for viewing categories easily I guess |
Sync/Download with other clients would be a nice to have but not really mandatory. I don't know if the Clients or the Protocol would support this. Also it's not so hard to add the Categories once in the clients. Using the Permission System would be nice too but I don't know how hard it would be. I mean a calendar isn't something that strangers would have access to and I would expect that people would intentionally mess things up. The core feature would be No. 1 and No. 2 just inside a Nextcloud for all Users. A more complicated calendar for big company use would require a more in depth permission system and more automation. I think this would be too much to ask for. |
I very much appreciate that calendar categories are now visible from the webinterface as well. But please refrain from syncing categories across clients. Esp when you share a calendar with others you do not want to see all their categories in your dropdown list nor would you like to use their colors. But I recommend to M. |
Hi,
|
Not sure, if I understand @MysticJay correctly, but imho syncing categories across clients is absolutely necessary. I definitely want to have the same categories that I have in the web interface on my phone as well as in my desktop application. Importing a shared calendar is probably a different thing. It would make sense to allow for 'do not import categories' or something similar. |
Well, please start an initiative for an RFC, but right now there is no standard for it. |
Here another user that would really appreciate creating a custom list of categories. As a workaround, I guess I could just change the default list in the source code of the instance? (I found a list in src/defaults/defaultCategories.js) And regarding syncing the list of categories:
Possibly of interest is RFC 7986 “New Properties for iCalendar”, which extends (see section 5.6) the CATEGORIES property to also be usable on the whole iCalendar object:
I have no idea if/which other software supports this, but it sounds like it may be suitable for this purpose. However one could also interpret the purpose as ‘listing the categories this calendar belongs to’, rather than ‘listing the categories its events can have’; I honestly do not know which meaning is intended. |
We have an events calendar of our club. Proposing again categories that were used before would already help. |
I have a similar request #3735. |
I'm a bit surprised this is open. I thought the Add a category to Calendar entries was implemented. Today I tried adding "Deadline" to one of my two NC instances and it did not work. Tried it via Ubuntu and Windows 11. |
Will this ever happen? Nextcloud calendar in it's current state is completely unusable for a lot of people because the categories are a mess. Also I think the month view should show the color of the category but i guess that's a topic for a separate ticket. |
Hi, This feature is really really needed for use Nextcloud Calendar for a lot of people... Any news ? |
Would really love an update on this! Waiting 3 years for a simple modification to a dropdown menu does not seem appropriate... |
@diabolicvincent-git you're probably right. Wanna give this a go? I can provide you with some pointers. |
If you can provide some advice to help anyone who can add this on the plugin, it'll be really helpfull I think. In fact I would love to do it but I'm not really confortable with the language used here :D |
…egories. This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used.
…egories. This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
are there configuration parameters for options like |
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de> WIP
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Co-authored-by: Anna <anna@nextcloud.com> Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de> WIP
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de> WIP
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de> WIP
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de> WIP
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
Hi team! Category visualization with colored tag in the year/month/week/day event view is a crucial feature, for example, to see past and future changes/features of events (remote or local event, event is completely closed or there is some documents left, etc.). Will it be added in future releases? |
One more voice here - being able to manage categories is crucial and a must (in my view) to be implemented (hopefully sooner than later)... |
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used. Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used.
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used.
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used.
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used.
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used.
This commit add all available "collaborative tags" and all already used categories into option groups of the tags-menu of the side-bar editor. Determining the set of already used categories is a little bit ugly: it used the oc_calendarobject_props table which might be considered "internal". However, this is the Nextcloud calendar app which only talks to the Nextcloud calendar server. So using this "internal ingredient" might be acceptable. This commit addresses and is a related to a couple of open issues: nextcloud#3735 Calendar Categories: Propose Categories already used - this should be fixed by this commit nextcloud#1644 Add own categories, delete default ones - this is partly fixed in the sense that collaboritive tags are now also proposed as calendar categories. - still default categories cannot be deleted - however, using option groups one at least has some sort of overview about the origin of the proposed category nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory - this issue is totally "ignored" by this commit as the proposed solution there is not needed (the categories are already there in the oc_calendarobject_props table) - that would have to be discussed there: but my impression that the tables and classed mentioned there are obsolete and no longer used.
Describe the solution you'd like
It would be nice if you could add own categories and delete default ones.
Additional context
With v2.0.0-beta2 and Issue #107 categories got added and so far it works. Categories from Thunderbird get shown in the web calendar and vice versa but it would be nice to delete unwanted default categories and add own categories for direct selection for the web calendar. I've looked into the files if there is an easy way to change this but as it looks, it isn't.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: