| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
nextcloud/backport-1972-invalid-files-from-scanner-9
[stable9] Make sure we don't scan files that can not be accessed
|
| |
| |
| |
| | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|/
|
|
| |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|
|
|
|
|
|
|
|
|
| |
When unsharing from self in a group share situation, the share items
passed to the post_unshareFromSelf hook were using the wrong format in
which the attribute names (ex: "share_type") have non camel-case format.
This fix makes sure that in group sharing case we use the correct
format. It looks like the code was already producing it but in
array_merge it was not using it and adding the unprocessed one.
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
|
|
| |
differs in case sensitivity
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|\
| |
| |
| |
| | |
nextcloud/backport-1558-remove-notifications-upon-user-deletion-9
[stable9] Remove notifications upon user deletion
|
| |
| |
| |
| | |
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>
|
|
|
|
| |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* 26342061b9b9767577a0f5eee16afd36e3b8b0b1
* 264aaf9ffaf71b2fc8a6bd2f5d5c9bf4a6d403de
|
| |
|
| |
|
|
|
|
|
|
|
| |
* if the compiled in version is older than the loaded version Nextcloud doesn't work
* uses the loaded libxml version to check against
fixes #205
|
| |
|
| |
|
|
|
|
| |
Upstream from https://github.com/owncloud/core/pull/25488
|
|\
| |
| | |
[stable9] Fix maintenance mode
|
| |
| |
| |
| |
| |
| | |
When the server is in maintenance mode, apps are not loaded.
That means apps/theming/ is not in the allowed paths. So we
need to check without autoloading, whether the class exists.
|
|/ |
|
|
|
|
| |
This reverts commit 9fcb26910e98282459fc7bf291f0a21275a1c919.
|
|
|
|
| |
This reverts commit 445a76bb1b0249a642a9a3f2e400c1221be7993f.
|
|
|
|
| |
This reverts commit 1a4297910496631542f65843ec30d65ee28d3b6e.
|
|\ |
|
| |
| |
| | |
The merge of the theming app changed these defaults back again.
|
| |
| |
| |
| | |
$nameSearchPattern was passed in and directly appended to the SQL query. Luckily the code path isn't reached anywhere in Nextcloud or the included apps.
|
| | |
|
| |\
| | |
| | | |
[stable9] getShareByToken() should also consider remote shares
|
| | | |
|
| |\ \
| | |/
| |/| |
[stable9] Add exemption for ACS endpoint
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In a SAML scenario we don't get any strict or lax cookie send for
the ACS endpoint. Since we have some legacy code in Nextcloud
(direct PHP files) the enforcement of lax cookies is performed here
instead of the middleware.
This means we cannot exclude some routes from the cookie validation,
which normally is not a problem but is a little bit cumbersome for
this use-case.
Once the old legacy PHP endpoints have been removed we can move
the verification into a middleware and also adds some exemptions.
Not super awesome code to have but the best that I could come up
with that doesn't add another ton of technical debt.
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The Nextcloud and ownCloud updaters allow someone to configure a custom release channel, this can then be used to publish different versions. (e.g. one channel stays on 9.x while another one already gets 10.x)
There is however one big problem with it: The value is effectively stored in the app config, which is stored in the database. So to be able to read the update channel a connection to the database is necessary. This is quite error prone and also causes some of the issues in the original ownCloud updater.
This moves the channel registration to the config.php and also includes a repair step.
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
* fixes #155
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
* Might fix an issue on oracle
|
| | | |
|