| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / /
| | |
| | |
| | | |
Signed-off-by: Alexander Piskun <bigcat88@icloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
|
|/ /
| |
| | |
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
|
| |
| |
| |
| | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|/
|
| |
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
|
|\
| |
| | |
[stable27] Fix issues where unencrypted_size was being falsely used for non-encrypted home folders
|
| |
| |
| |
| | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
| |
| |
| |
| | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we didn't find the "$lastKnownComment" the whole condition was ignored.
Now we still use the ID as an offset.
This is required as a fall-back for expired messages in Talk
and deleted comments in other apps.
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
| |
| |
| |
| | |
Signed-off-by: Lucas Azevedo <lhs_azevedo@hotmail.com>
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Fixes #40064.
This could be fixed by adding a rollback and starting a new transaction
before the SELECT query, but in this case that would have the same
effect as not using one.
See https://dev.mysql.com/doc/refman/8.0/en/innodb-autocommit-commit-rollback.html
and https://www.postgresql.org/docs/7.1/sql-begin.html#R1-SQL-BEGIN-1
Signed-off-by: Lucas Azevedo <lhs_azevedo@hotmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
apcu lead to side effects especially with app management and (soft)
inter-dependencies, and lead also to 500 server errors. While we could
add management to clear apcu cache in many cases (may stil leave edge
cases) the performance benefit is marginally as also class maps are
already cached in opcache. Hence, the simple and effective way to go is
to not use apcu for autoloading.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|
|
|
| |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|
|
|
| |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|
|
|
| |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\
| |
| | |
[stable27] Detect aborted connection in OC\Files\View and stop writing data to t…
|
| |
| |
| |
| |
| |
| | |
output buffer
Signed-off-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Anna Larch <anna@nextcloud.com>
|
|\ \
| |/
|/| |
[27] move share permission logic to storage wrapper
|
| |
| |
| |
| | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
| |
| |
| |
| |
| |
| | |
this way we only have to determine the share permissions once
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \
| | |
| | | |
[stable27] enh: skip processing for empty response
|
| |/
| |
| |
| | |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|\ \
| | |
| | | |
[stable27] fix: prevent sharing permissions on user root folder
|
| |/
| |
| |
| | |
Signed-off-by: John Molakvoæ <skjnldsv@protonmail.com>
|
|/
|
|
|
|
|
|
| |
If 'verify_bucket_exists' is set to false in the config.php s3 configuration, it's supposed to avoid
verifying that the bucket exists. However empty(falsy) will always return true, so this condition
would not work.
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|
|
|
| |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|\
| |
| | |
[stable27] fix(cache): Remove displayname cache entry on delete
|
| |
| |
| |
| | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
| |
| |
| |
| | |
Signed-off-by: Anna Larch <anna@nextcloud.com>
|
| |
| |
| |
| | |
Co-authored-by: Benjamin Gaussorgues <benjamin.gaussorgues@nextcloud.com>
Signed-off-by: Côme Chilliet <91878298+come-nc@users.noreply.github.com>
|
|/
|
|
|
|
| |
disabled users
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
|
|
|
|
|
| |
Calling setHeaders(getHeaders()) breaks the CSP nonce for unknown reasons
So shifting back to old standard practise for now
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
|
|
| |
sleep
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
|
|
| |
Similar to the ratelimit backend
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Anna Larch <anna@nextcloud.com>
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Overwrite the display name after the account is initialized
when using an instacne of IGetDisplayNameBackend.
Before when using a variation of user_oidc and registering
a Backend.php implementing IGetDisplayNameBackend
the personal setting page shows 'uid'.
The UserManager/AccountManager seems not to use consistently
the correct backend.
The correct backend is used in this sequence:
server/lib/private/TemplateLayout.php
$userDisplayName = \OC_User::getDisplayName();
$this->assign(user_displayname, $userDisplayName);
In the settings page, it definitely not calls the registered backend,
but seems to fall back to default Backend and shows (usually) uid
or a value from the standard account property table.
Signed-off-by: Max <max@nextcloud.com>
|
|/
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
|
|
| |
this seems to improve mariadbs index selection
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ |
|
| |
| |
| |
| | |
Co-authored-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
Signed-off-by: John Molakvoæ <skjnldsv@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OC\Files\Cache\Cache::get can return string|false|null, not just string|false.
- nextcloud/server#26270 added handling of false, but null is needed too.
- Well, or we change the default $resullt to false, but I'm not sure if that has other ramifications and the real need here is to simply catch situations where the cache source storage path is not valid for whatever reason
Related: nextcloud/server#19009
Signed-off-by: Josh Richards <josh.t.richards@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Simon L <szaimen@e.mail.de>
|