| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
nextcloud/fix/caldav/shared-calendars-activity-umlauts
fix(caldav): encode calendar URIs with umlauts for activities
|
| | |/ /
| |/| |
| | | |
| | | | |
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
|
|\ \ \ \
| |/ / /
|/| | | |
fix(dav): Try basic auth for ajax WebDAV requests
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
nextcloud/fix/dav/limit-sync-token-created-at-updates
fix(dav): Limit number of UPDATES for sync token created_at
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Address book and calendar sync tokens have a created_at column in 26+
and we need to assign a current timestamp to the existing data at
upgrade so the data isn't cleaned up immediately. Updating the full
table is expensive and fails on clustered setups that limit transaction
size. We don't need a timestamp for the oldest rows so we can skip
updating them.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
|
|/ /
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
|
| |
| |
| |
| |
| |
| | |
There is already a webhooks application in the appstore
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/bugfix/noid/sensitive-dav-forbidden-logging
fix(dav): Don't log access control as error
|
| | |
| | |
| | |
| | | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Anna Larch <anna@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Andrew Summers <18727110+summersab@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Synced from LDAP to profile:
- Date of birth
Synced from LDAP to SAB (via the profile):
- Biography
- Date of birth
Original code by Jake Nabasny (GitHub: @slapcat)
Co-authored-by: Jake Nabasny <jake@nabasny.com>
Co-authored-by: Richard Steinmetz <richard@steinmetz.cloud>
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
nextcloud/bug/noid/caldav-search-limit-and-timerange
CalDAV fix search with limit and time range
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Sorting the events by the start date leads to more predictable results for the search API consumers.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Event recurrences are evaluated at runtime because the database only knows the first and last occurrence.
Given, a user created 8 events with a yearly reoccurrence and two for events tomorrow.
The upcoming event widget asks the CalDAV backend for 7 events within the next 14 days.
If limit 7 is applied to the SQL query, we find the 7 events with a yearly reoccurrence and discard the events after evaluating the reoccurrence rules because they are not due within the next 14 days and end up with an empty result even if there are two events to show.
The workaround for search requests with a limit and time range is asking for more row than requested and retrying if we have not reached the limit.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
|
|\ \ \
| | | |
| | | | |
Add SPDX header - batch 7
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
|
|\ \ \ \
| |/ / /
|/| | | |
fix(dav): Rate limit address book creation
|
| | |/
| |/|
| | |
| | | |
Signed-off-by: Hamza Mahjoubi <hamzamahjoubi221@gmail.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
|
| |
| |
| |
| | |
Signed-off-by: Jérôme Herbinet <33763786+Jerome-Herbinet@users.noreply.github.com>
|
| |
| |
| |
| | |
Signed-off-by: Anna Larch <anna@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
| |
| |
| |
| | |
Signed-off-by: Anna Larch <anna@nextcloud.com>
|
|\ \
| | |
| | | |
Do not load IMipPlugin before user session is initialized also use userSession instead of userId in constructor.
|
| | |
| | |
| | |
| | | |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
| |/
|/|
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|/
|
|
| |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|