Save VEVENT CATEGORIES as vcategory #29950
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
enhancement
feature: caldav
Related to CalDAV internals
feature: dav
integration
Comments
tcitworld
added
enhancement
0. Needs triage
|
Hi there, I am in the progress to give the calendar app at least the possibility to let the admin define further default categories. Now concering this open issue: my impression is that neither vcategory nor vcategory_to_object is used for anything at the moment. The initial comment at the top of this issue states that file-categories are saved in these tables. But that does not seem to be the case. At least the "collaborative" tags seemingly do not affect these two left-over database table. Could perhaps someone with more insight in the code clarify if these two category tables are anywhere used? In my NC instances those tables only have some leftover categories related to calendar events, but nothing relating to files. |
|
The table |
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
…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: - this should be fixed by this commit - 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.
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
…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: - this should be fixed by this commit - 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.
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
…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.
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
…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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 24, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 25, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 25, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 25, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 25, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 25, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 25, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 25, 2023
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
It's currently only used for the favorite status of a file (the special value I still would prefer to extract At the same time it would be nice to reuse existing tags from files, contacts…in calendar and other apps as well. |
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 27, 2023
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. Co-authored-by: Anna <anna@nextcloud.com> Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
May 10, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
May 14, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Jun 16, 2023
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
ChristophWurst
pushed a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Jun 28, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Jul 11, 2023
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
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Aug 3, 2023
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
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Aug 8, 2023
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
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Sep 10, 2023
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
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Nov 24, 2023
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Jan 6, 2024
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Feb 23, 2024
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 8, 2024
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 8, 2024
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Apr 28, 2024
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
May 1, 2024
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>
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
May 15, 2024
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.
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
May 21, 2024
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.
|
Fixed with nextcloud/calendar#5161 |
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Aug 17, 2024
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.
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Aug 26, 2024
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.
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Aug 28, 2024
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.
rotdrop
added a commit
to rotdrop/nextcloud-app-calendar
that referenced
this issue
Aug 29, 2024
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently only files tags are saved into
vcategoryandvcategory_to_object. We should extractCATEGORIESfromVEVENTs when saving/updating an event and insert them here.Then they can be queried by the calendar app through DAV's TagsPlugin (or OCS ?), in order to be suggested in the calendar app.
The text was updated successfully, but these errors were encountered: