| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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: skjnldsv <skjnldsv@protonmail.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
|/
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
[stable29] fix(files): Ensure renaming state is correctly reset
|
| |
| |
| |
| | |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
| |
| |
| |
| |
| |
| | |
TODO: Drop when we support Node 22.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Is a node is renamed and the new name is out of the current
visible list of nodes the component will be recycled, this means
the props will change, so when the `onRename` functions is about to reset
the state the `this.source` will point to a different node.
To fix this, but also to separate business logic from visual representation,
the logic is moved into the renaming store and the component is only
responsible for rendering.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|\ |
|
|/
|
|
| |
Signed-off-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Simon L. <szaimen@e.mail.de>
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
| | |/
| |/|
| | |
| | | |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \
| |/
|/| |
[stable29] chore: request review from groupware when changing the card- and cald…
|
| |
| |
| |
| | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
| |
| |
| |
| | |
Signed-off-by: Marcel Müller <marcel-mueller@gmx.de>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
| |
| |
| |
| |
| |
| | |
Ref https://github.com/nextcloud/groupware?tab=readme-ov-file#components-and-roles
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|/
|
|
| |
Signed-off-by: Marcel Klehr <mklehr@gmx.net>
|
|
|
|
| |
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: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
|
|\ \
| | |
| | | |
[stable29] perf(ObjectStoreStorage): Improve (slow) move on same object bucket
|
| | |
| | |
| | |
| | |
| | |
| | | |
Some are still failing
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit fixes the issue #47856. When you upload a file into a group folder and when you use a single S3 bucket as primary storage, the final move operation hangs for a long time. In the background, Nextcloud initiates a copy-delete sequence from the bucket into the bucket, with causes a lot unnecessary overhead. Nextcloud thinks that the file must be imported to another storage and does not recognize that everything is done on the same object bucket. In that case, the import step can be completely skipped, which saves time, network bandwidth and reduces the load on the object storage.
The behavior improves a lot with https://github.com/nextcloud/server/pull/46013. However, there are still some put messages that are being sent to the object storage when you use an object storage as primary storage and upload files into a group folder.
Co-authored-by: Kate <26026535+provokateurin@users.noreply.github.com>
Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
|
|\ \ \
| | | |
| | | | |
[stable29] fix(ShareEntryLinkList): Append new links to the end of list
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently new shares are added to beginning of the share list in the UI
messing up the ordering with the original (first) looking like the most
recent and the most recent looking like the original share. This error
disappears on refresh.
Resolves : https://github.com/nextcloud/server/issues/48415
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
|\ \ \
| | | |
| | | | |
[stable29] fix(files-external): set password as sensitive
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
|
|\ \ \
| | | |
| | | | |
[stable29] Fix disabled user list for subadmins
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|