The underlying issue has been fixed upstream.
This reverts:
- c5b5f162e0 (#4431)
- 5334250382 (#4646)
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
Abusing the appointment config endpoint can lead to additional server
load. Sending bulks of booking requests can lead to mass notifications
and emails and server load, too.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
This commit adds support for adding circles as attendees to a calendar event.
The relationship between the imported group and members will be compliant with
the iCal specification.
A circle with the title "testcircle" will be added as an attendee with iCal
attributes "CUTYPE=GROUP` and uri "mailto:circle+CIRCLEID@CIRCLE_INSTANCE".
Members of the circle will be imported as standard attendees. Each member gets
assigned to the circle group entry by assigning them to the group uri using the
iCal member property: "MEMBER='mailto:circle+CIRCLEID@CIRCLE_INSTANCE'".
Searching for circles is only enabled if the circles app is activated.
Circles added to the list of attendees get imported only once and are not
synced yet. While adding a circle, a notice about this is shown to the user.
Only members of local circles which are local users get imported.
Rendering groups in the frontend is done in a separate PR
https://github.com/nextcloud/calendar/pull/5396
Signed-off-by: Jonas Heinrich <heinrich@synyx.de>
Implement ability to render groups and group members as attendees of an
calendar event. This is implemented by reading and interpreting the
CUTYPE and MEMBER parameter of the iCal ATTENDEE attribute.
For example attendee "user1" belongs to a group identified with the uri
mygroup@localhost: "ATTENDEE;MEMBER="mailto:mygroup@localhost";CN=user1;[...]".
The group entity is also a ATTENDEE entry but with "CUTYPE=GROUP" and
with the corresponding uri mygroup@localhost:
"ATTENDEE;CN=MyGroup;CUTYPE=GROUP;[...]:mailto:mygroup@localhost".
In the frontend, groups will be displayed as a collapsible list whereas
members of the group will be displayed with the same functionality as
normal attendees.
In case the group entry gets deleted, all of its members will get
removed too.
Empty groups with no members might be present in the iCal file but won't
get rendered.
According to the iCal specifications, groups can have more than one uri and
attendees could have multiple membership addresses in one attribute.
This is neither covered yet in calendar-js nor in this PR.
Signed-off-by: Jonas Heinrich <heinrich@synyx.de>
The old, bundled widget has to stay until we exclusively support the
corresponding server versions.
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
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/calendar#3735 Calendar Categories: Propose Categories already used
- this should be fixed by this commit
nextcloud/calendar#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>
The public calendar view used 'base' Template responses, preventing the footer that's being used on other public sharing pages from showing. This makes use of PublicTemplateResponse to show it automatically. It's however hidden on embed view.
Reference: https://help.nextcloud.com/t/feature-request-impressum-and-privacy-declaration-links/161162
Signed-off-by: Thomas Citharel <tcit@tcit.fr>