| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
Actually return the root folder when traversing up the tree
|
|/
|
|
|
|
|
|
| |
If you now keep calling $node->getParent() you will at some point get
the RootFolder back. This is a nice termination check and will prevent
endless loops if an exit condition is slightly off.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| |
|
| |
|
|\
| |
| | |
[stable13] Remove cookies from Clear-Site-Data Header
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
In https://github.com/nextcloud/server/commit/2f87fb6b456fd109c90a5093c31b7a3f62a32040 this header was introduced. The referenced documentation says:
> When delivered with a response from https://example.com/clear, the following header will cause cookies associated with the origin https://example.com to be cleared, as well as cookies on any origin in the same registered domain (e.g. https://www.example.com/ and https://more.subdomains.example.com/).
This also applies if `https://nextcloud.example.com/` sends the `Clear-Site-Data: "cookies"` header.
This is not the behavior we want at this point!
So I removed the deletion of cookies from the header. This has no effect on the logout process as this header is supported only recently and the logout works in old browsers as well.
Signed-off-by: Patrick Conrad <conrad@iza.org>
(cherry picked from commit 1806baaeafa284808cceb1a38ea2e1a9189d0407)
|
| |
|
|\
| |
| |
| |
| | |
nextcloud/bugfix-stable13/noid/forbid_freebusy_but_allow_local_delivery
[stable13] allow local delivery of schedule message while prohibiting FreeBusy requests
|
| |
| |
| |
| |
| |
| | |
collection. This allows to keep local delivery of scheduling messages while prohibiting FreeBusy requests
Signed-off-by: Georg Ehrke <developer@georgehrke.com>
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/stable13-11967-fix-opening-a-section-again-in-the-files-app
[stable13] Fix opening a section again in the Files app
|
| | |
| | |
| | |
| | | |
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The custom handler for "URL changed" events were added to reload the
file list whenever the sections for favorites and shares were opened;
this was used to fix the problem of not reloading the file lists when
opening them for a second time. However, besides that the handlers were
not really necessary, and as the root of the bug was fixed in the
previous commit those handlers are now removed.
The file list for tags uses the handler for a different purpose, though,
so that one was kept.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a section is open in the Files app a "show" event is triggered.
File list objects handle that event by reloading themselves, but only
if the file list was shown at least once. However, the file list objects
of plugins are created when the "show" event is triggered for the first
time for their section; as the file list objects register their handler
for the "show" event when they are created they never handle the first
triggered "show" event, as the handler is set while that event is being
already handled. Therefore, from the point of view of the handler, the
second time that a "show" event was triggered it was seen as if the file
list was shown for the first time, and thus it was not reloaded. Now the
"shown" property is explicitly set for those file lists that are created
while handling a "show" event, which causes them to be reloaded as
expected when opening their section again.
Note that it is not possible to just reload the file list whenever it is
shown; the file list is reloaded also when the directory changes, and
this can happen when the web page is initially loaded and the URL is
parsed. In that case, if file lists were reloaded when shown for the
first time then it could be reloaded twice, one with the default
parameters due to the "show" event and another one with the proper
parameters once the URL was parsed, and the files that appeard in the
list would depend on which response from the server was received the
last.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|\ \ \
| | | |
| | | | |
lazy open first source stream in assemblystream
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \ \ \
| |/ / /
|/| | | |
[13] Do not emit preHooks twice on non-part-storage
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
The old code would emit the hooks twice. Thus having the version written
twice. Which is not very performant as it is first read twice as well.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/bugfix-stable13/9326/make_sure_usermanager_getByEmail_only_returns_IUser
[stable13] filter null values for UserManager::getByEmail
|
| |/
| |
| |
| | |
Signed-off-by: Georg Ehrke <developer@georgehrke.com>
|
|\ \
| |/
|/|
| |
| | |
nextcloud/backport/11972/fix-l10n-fetching-from-theme-13
[stable13] Load apps/APP/l10n/*.js and themes/THEME/apps/APP/l10n/*.js
|
|/
|
|
|
|
| |
Before it quit right after finding the theme version of the l10n file which results in a not translated part of the UI.
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\
| |
| |
| |
| | |
nextcloud/backport/10942/longer-password-reset-time
[stable13] Change password expiration time from 12h to 7d
|
|/
|
|
|
|
| |
We use the same logic for creating accounts without a password and there the 12h is a bit short. Users don't expect that the signup link needs to be clicked within 12h - 7d should be a more expected behavior.
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\
| |
| |
| |
| | |
nextcloud/stable13-11756-ignore-session-lifetime-if-it-can-not-be-converted-to-a-number
[stable13] Ignore "session_lifetime" if it can not be converted to a number
|
|/
|
|
|
|
|
|
|
|
|
| |
When "session_lifetime" can not be converted to a number the interval
becomes a NaN due to dividing it by 2. This NaN was "dragged" over all
the other mathematical operations and caused the heartbeat to be post
again and again due to an infinite loop with no pauses in "setInterval".
Now, the interval is set to the default value instead if the
"session_lifetime" can not be converted to a number.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|\
| |
| | |
13.0.7
|
|/
|
|
| |
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\
| |
| | |
[stable13] Fix a misleading setup check for .well-known/caldav & carddav
|
|/
|
|
|
|
| |
The problem is that the version without the slash is the correct one.
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
| |
|
|\
| |
| | |
13.0.7 RC 2
|
|/
|
|
| |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\
| |
| | |
[13] Allow the creationg of previews of files stored in appdata
|
| |
| |
| |
| |
| |
| |
| | |
To allow us to create previews of files stored in appdata we need to
construct the view differently.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \
| |/
|/| |
[stable13] Update CRL due to changed cert for linkshareex
|
|/
|
|
|
|
| |
See https://github.com/nextcloud/app-certificate-requests/pull/193
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
13.0.7 RC 1
|
| |
| |
| |
| | |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|/
|
|
|
|
|
|
| |
For some reason the docker image does not setup the permissions correctly,
by using a different name the nextcloud installer will create the database instead
with the correct permissions
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
| |
|
| |
|