| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
make 'text-overflow: ellipsis' possible again in dashboard
|
| |
| |
| |
| |
| | |
Signed-off-by: Artur Neumann <artur@jankaritech.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/fix/replace-opis-closure-by-laravel-fork
Replace opis/closure by laravel/serializable-closure
|
| | |
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
We need to be able to unserialize data from before upgrade.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
nextcloud/fix/remove-at-matcher-in-user_ldap-tests
Remove deprecated at() matcher from user_ldap tests
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|\ \ \ \
| | | | |
| | | | | |
Remove at matcher in theming tests
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Remove at matcher uses in tests/lib
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| |/ / /
| | | |
| | | |
| | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \ \
| | | | |
| | | | | |
l10n: Spelling unification
|
| | | | |
| | | | |
| | | | | |
Signed-off-by: Valdnet <47037905+Valdnet@users.noreply.github.com>
|
| | | | |
| | | | |
| | | | | |
Signed-off-by: Valdnet <47037905+Valdnet@users.noreply.github.com>
|
| | | | |
| | | | |
| | | | | |
Signed-off-by: Valdnet <47037905+Valdnet@users.noreply.github.com>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix email shares not being shown to other users
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix profiler trying to serialize invalid utf8
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The cookie value contains invalid utf8 characters most of the time so
let's just ignore it as it is also not that interesting to analyse.
Signed-off-by: Carl Schwan <carl@carlschwan.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>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Mention missing files subdir
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Many users are getting confused by the inaccurate error message "Home storage for user $user not writable" because the storage *is* writable. The actual issue is a missing files/ subdirectory. cf. https://help.nextcloud.com/t/home-storage-for-user-not-writable/10831/7
By mentioning the possible cause in the error message, users are going to be able to rapidly solve their problem rather than bang their heads against the screen, Google, and eventually forums to find out that the error message is wrong in their case.
Yes, it would be better to detect and precisely describe the fault, or fix the problem automatically, but until then, be kind to the users for the next however many years.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | | |
Fix logger overwriting vars in some circumstances
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Use {$var} instead of ${var} for PHP 8.2 compatibility
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | | |
nextcloud/fix-default-toast-message-for-failed-uploads-with-http2
Fix default toast message for failed uploads with HTTP/2
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When an upload fails a toast is shown with either a specific message or
just the textual part of the HTTP error code (which comes from the
upload failure handler and set by "jQuery.ajax()". However, if there
is neither a message nor an error then the toast will show the default
message from the Toastify-js library, which is an undescriptive "Hi
there!".
When HTTP/2 is used Chromium does not provide the textual part of the
HTTP error code, so when an upload fails the toast can receive an empty
message and thus just show "Hi there!". Now an explicit message is
provided as a fallback to prevent that.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Make sure ResetTokenBackgroundJob doesn't execute if config is read-only
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
No need to try to delete the config key in config.php if we aren't
allowed to.
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \ \ \
| | | | |
| | | | | |
Handle the move operation properly between shared calendars
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Introduce a new CalendarObjectMovedEvent typed event dedicated for
this operation
- Handle the event in the activity backend and add new appropriate activity subjects
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|\ \ \ \
| |/ / /
|/| | | |
Fix 2FA setup vs set up typo
|