| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Co-authored-by: Ferdinand Thiessen <opensource@fthiessen.de>
Co-authored-by: Côme Chilliet <91878298+come-nc@users.noreply.github.com>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
|
|
|
|
|
|
|
| |
We basically mock the way `URLGenerator::getAbsoluteURL` works,
so we must make sure that the URL might already contain the webroot.
Because `baseURL` and `cliURL` also contain the webroot we need to remove
the webroot from the URL first.
Co-authored-by: Ferdinand Thiessen <opensource@fthiessen.de>
Co-authored-by: Daniel <mail@danielkesselberg.de>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|\
| |
| | |
[stable30] chore(i18n): adapted lowercase
|
| |
| |
| |
| | |
Signed-off-by: rakekniven <2069590+rakekniven@users.noreply.github.com>
|
| |
| |
| |
| |
| | |
Reported at Transifex
Signed-off-by: rakekniven <2069590+rakekniven@users.noreply.github.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>
|
|
|
|
|
|
| |
trusted domains as last fallback.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|
|
|
|
|
|
|
|
|
| |
trusted_domains.
1) The checks for well-known urls should always run against the root domain and therefore the option to remove the webroot.
2) For trusted domains, the available protocol is unknown, and thus some guesswork would be needed to make that work. I've decided for now to not consider them anymore to reduce false-positives.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
|
|
|
| |
not working
Signed-off-by: provokateurin <kate@provokateurin.de>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
|
|
|
|
| |
Signed-off-by: Marcel Klehr <mklehr@gmx.net>
(cherry picked from commit c8f4967ce2a41c19ab17665e3330183b4a133dab)
|
|
|
|
|
| |
Signed-off-by: Marcel Klehr <mklehr@gmx.net>
(cherry picked from commit 44a5723973ad93e340fdbc2810c975e667f1e51e)
|
|
|
|
|
|
|
|
|
| |
1. The "recent" accounts API only works for admin and delegated admin -> hide for group managers
2. Group managers can not create new groups -> Hide the UI to add a new group for them
3. Accounts created by group managers require one of the groups, which is managed by the group manager, assigned.
So if the group manager only manageres a single group, we should preselect that group.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.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>
|
|
|
|
|
|
|
|
|
| |
textprocessing settings
TaskProcessing is transparent to textprocessing providers and TextProcessing can use Taskprocessing providers so these are unnecessary
Signed-off-by: Marcel Klehr <mklehr@gmx.net>
Signed-off-by: Julien Veyssier <julien-nc@posteo.net>
|
|
|
|
|
|
|
| |
taskprocessing is transparent to STT providers so specific STT settings are obsolete
Signed-off-by: Marcel Klehr <mklehr@gmx.net>
Signed-off-by: Julien Veyssier <julien-nc@posteo.net>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Jérôme Herbinet <33763786+Jerome-Herbinet@users.noreply.github.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: Andy Scherzinger <info@andy-scherzinger.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
| |
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
[stable30] fix(security): Update expiration date in security.txt
|
| |
| |
| |
| | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|/
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
| |
| |
| |
| |
| |
| | |
possible
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.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>
|