| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
28.0.7 RC1
|
| |
| |
| |
| | |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|\ \
| | |
| | | |
[stable28] Show non writable folders during move or copy
|
| | |
| | |
| | |
| | | |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|/ /
| |
| |
| | |
Signed-off-by: Louis Chemineau <louis@chmn.me>
|
|\ \
| | |
| | | |
[stable28] fix(files_sharing): Add one string for every share type + fix(sharingDetails): Show correct share target
|
| | |
| | |
| | |
| | | |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The share details page should show the target email or user/server to which
the user is creating the share.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
[skip ci]
|
| | |
| | |
| | |
| | |
| | |
| | | |
language
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Louis Chemineau <louis@chmn.me>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \ \
| | | | |
| | | | | |
[stable28] Respect empty `expiryDate` value in server
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Verify that explicitly sending empty `expireDate` param to server overwrite default
and sets not expiry date, if non is enforced.
- Update tests to avoid converting empty string to date.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If `expireDate` is an empty string and not `null` then the server should not set a default.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
|/ / / /
| | | |
| | | |
| | | | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \ \ \
| | | | |
| | | | | |
[stable28] fix(ObjectStore): Fix regression when hostname is empty
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes #45637
The support for s3-accelerate added in #44496 introduced a regression in AWS S3 environments when `hostname` is blank (which is a valid configuration w/ AWS since the hostname gets auto-generated).
Signed-off-by: Josh <josh.t.richards@gmail.com>
|
|\ \ \ \
| |_|/ /
|/| | | |
[stable28] feat: add option to disable scanner transactions
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \ \
| |/ /
|/| | |
[stable28] get child ids for folder in a separate query during move
|
|/ /
| |
| |
| | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \
| | |
| | | |
[stable28] Use isRetryable to catch retryable exceptions
|
| | |
| | |
| | |
| | | |
Signed-off-by: Louis Chemineau <louis@chmn.me>
|
|\ \ \
| | | |
| | | | |
[stable28] fix(files): do not rely on unique fileid
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
|\ \ \ \
| | | | |
| | | | | |
[stable28] 44032 fix show new shares without refresh
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These changes fixes the issue of having the refresh the UI after share creation, as the share is not
immediately removed from the UI list.
Important changes
- The basis of checking wether a password/expire date is no longer based on config values alone
because the config is not expected in a share creation circle. Hence we check the configs and check
if the share object (this.share) has the expected values set. This way, once the required properties
are set, code control does not enter the block meant to handle the setting of required properties
unneccessarily.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
| |/ / /
| | | |
| | | |
| | | | |
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \
| | | |
| | | | |
[stable28] test: add tests for ProfilePageController
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|\ \ \ \
| |/ / /
|/| | | |
[stable28] fix: Only list remnants as disabled if option is enabled
|
| |/ /
| | |
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Louis Chemineau <louis@chmn.me>
|
|\ \ \ |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.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: skjnldsv <skjnldsv@protonmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
|\ \ \ \
| |/ / /
|/| | | |
[stable28] fix(Session): avoid password confirmation on SSO
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- "password-unconfirmable" is the effective name for 30, but a draft
name was backported.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
SSO backends like SAML and OIDC tried a trick to suppress password
confirmations as they are not possible by design. At least for SAML it was
not reliable when existing user backends where used as user repositories.
Now we are setting a special scope with the token, and also make sure that
the scope is taken over when tokens are regenerated.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|