| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
[stable28] fix(appstore): Ensure returned apps from AppStore are valid
|
| |
| |
| |
| | |
Co-authored-by: Côme Chilliet <91878298+come-nc@users.noreply.github.com>
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
fix: lint
chore: remove space
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
fix: check if response array is null
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
chore: Add log
|
|\ \
| | |
| | | |
[stable28] fix: Do not try to set HTTP response code on already closed connection
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This avoids a PHP warning in the logs about trying to set the response
code while the output already started. It’s useless to try to print an
error page anyway in this situation because the connection was closed
already.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|\ \ \
| | | |
| | | | |
[stable28] fix(BaseResponse): Cast XML element values to string
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Julius Knorr <jus@bitgrid.net>
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | |/ /
| |/| |
| | | |
| | | | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
|/ /
| |
| |
| | |
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: Louis Chemineau <louis@chmn.me>
|
|
|
|
|
|
| |
This is to prevent collision as we are sometime hashing user input, yet using that hash to target the background job in the database.
Signed-off-by: Louis Chemineau <louis@chmn.me>
|
|\
| |
| | |
[stable28] fix(files): Create non-existent parents of mountpoints
|
| |
| |
| |
| | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
| |
| |
| |
| | |
Signed-off-by: Marcel Müller <marcel-mueller@gmx.de>
|
|/
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Co-authored-by: Côme Chilliet <91878298+come-nc@users.noreply.github.com>
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Storages that do not have a dedicated owner (e.g. groupfolders, external
storages) currently always assume the current session user as the owner.
This leads to several issues when there is no user session but a node is
obtained through a user folder.
In order to have the correct user available we need to pass the user
that is used to setup a mountpoint along to the storage layer as we
generally assume that an owner is available for those.
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
|
|
|
| |
Signed-off-by: Julien Veyssier <julien-nc@posteo.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>
|
|
|
|
|
|
|
| |
Make changes recently added via #44230 match #8188 to avoid failures in restricted hosting environments.
Fixes #47562
Signed-off-by: Josh <josh.t.richards@gmail.com>
|
|\
| |
| | |
[stable28] fix(webauthn): Increase database column for public key id
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Resolves https://github.com/nextcloud/server/issues/34476
There is no maximum length defined in the standard,
most common the length is between 128 and 200 characters,
but as we store it not in plain data but base64 encoded the length can grow about 1/3.
We had a regression with 'Nitrokey 3' which created IDs with 196 byte length -> 262 bytes encoded base64.
So to be save we increase the size to 512 bytes.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|/
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
|
|
|
|
| |
Signed-off-by: Christoph Klaffl <christoph@phreaker.eu>
|
|
|
|
| |
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: Joas Schilling <coding@schilljs.com>
|