| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
[stable27] Return correct status if touch failed
|
| |
| |
| |
| | |
Signed-off-by: Louis Chemineau <louis@chmn.me>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \
| | |
| | | |
[stable27] fix(ldap): store last known user groups
|
| | |
| | |
| | |
| | | |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
| | |
| | |
| | |
| | |
| | |
| | | |
- for LDAP user life cycle management
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|\ \ \
| | | |
| | | | |
[stable27] fix(files_external): on case insensitive system, block case change
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a file/directory is renamed to the same name with only case change,
the rename fail. We block this kind of rename.
The user will have to rename to another name first.
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: Nextcloud bot <bot@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/fix/39565/race-condition-on-web-files-view
fix(files): race condition on web files view change
|
| | |
| | |
| | |
| | |
| | |
| | | |
It is handled by new navigation with Vue
Signed-off-by: Grigorii K. Shartsev <me@shgk.me>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Grigorii K. Shartsev <me@shgk.me>
|
|/ /
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \
| |/
|/| |
[stable27] fix: Don't try to access null array
|
| |
| |
| | |
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| |
| |
| |
| | |
Allow download was duplicated via a rebase/merge action during
fe78157b77675b2fdc9eb5abfe0d530727fdddd8 this fixes that.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`isDefaultExpireDateEnforced` and its corresponding `defaultExpirationDate`
is currently treated as the enforcement fallback when share type enforcements are not
set.
However, `isDefaultExpireDateEnforced` and `defaultExpirationDate` are actually more like
`isDefaultPublicExpireDateEnforced` and `defaultPublicExpirationDate` and therefore only applies
to public shares.
It might be ideal to rename this variables all the way from the backend config to the way we use
them in the frontend code.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Current expiration date errorneously assumes that `defaultExpirationDate`
applies to all kinds of shares. But it only really applies to public shares despite
its name.
This commit, fixes that by paring expiration dates with the correct share types during
new share initialization and simplifying the `hasExpirationDate` (check) property.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We should check that a maximum expiry date has been enforced for
all shares and NOT JUST FOR internal shares before enforcing a UI max date,
like in commit 9757e680e2f643fe19432255c4142e96fbc88df5
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, users could change the share expiry date up
to the enforced maximum.
The new share flow imposed the enforced share expiry
date maximum literally and did not allow even dates
lower than the maximum enforced.
That does not make much sense, if the enforced expiry date is 30
days from creation date, then it's logical to allow users set the
date to anything less than 30 days from the creation date.
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
|
|/
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Jonas <jonas@freesources.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes workflows on groupfolders, as it will consider access to
files in groupfolders.
It also fixes false positives where access to files was limited by other
means not taken into account before, e.g. access control.
For postDelete events, check for permissions of the parent folder
instead, as the file itself no longer exists.
Fixes: nextcloud/flow_notifications#71
Signed-off-by: Jonas <jonas@freesources.org>
|
|
|
|
| |
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: 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: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|