| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
owncloud/fs-initmountpoint-rethrowifusernotfoundagain
Mark $usersSetup only if user was found in initMountPoints
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
initMountPoints is marking a user as successfully initialized too
early. If the user was not found an NoUserException was thrown, the
second time initMountPoints is called would not rethrow the exception
and happily continue.
This fix makes sure that we consistently throw NoUserException when
initMountPoints is called repeatedly with invalid users.
|
| | |
|
|\ \
| |/
|/| |
App migration steps need to push feedback to the user ....
|
| | |
|
|\ \
| | |
| | | |
Change the sort order of background jobs to be DESC instead of ASC
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In theory, if your instance ever creates more jobs then your system cron can
handle, the default background jobs get never executed anymore. Because
everytime when the joblist returns the next job it looks for the next ID,
however there is always a new next ID, so it will never wrap back to execute
the low IDs. But when we change the sort order to be DESC, we make sure that
these low IDs are always executed, before the system jumps back up to
execute the new IDs.
|
|/ /
| |
| |
| |
| |
| |
| | |
In some scenarios initMountPoints is called with an empty user, and
also there is no user in the session.
In such cases, it is unsafe to let the code move on with an empty user.
|
|/ |
|
|\
| |
| | |
Enc master key improvements
|
| | |
|
|\ \
| | |
| | | |
SharedStorage to new sharing code + cleanup
|
| | | |
|
|\ \ \
| | | |
| | | | |
When calling file_put_contents clear the checksum
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes #23782 and #23783
If the file scanner detects a changed file we clear the checksum while
we update the cache.
* Unit test added
|
|\ \ \
| | | |
| | | | |
Move the group dummy backend to test
|
| |/ /
| | |
| | |
| | |
| | | |
The dummy backend is only used for testing and should thus reside in
tests.
|
|\ \ \
| | | |
| | | | |
Introduce isReadyForUser and verify in file transfer ownership
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
Add data-fingerprint property
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Move post_removeFromGroup to shareManager
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The last sharing hook to be moved over.
* Added unit tests
* Removed old tests that relied on old behaviour
* Removed old hooks.php
|
| | | | |
| | | | |
| | | | |
| | | | | |
Testable code. Yay.
|
| | | | | |
|
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | | |
UID and login name are two different things.
|
| | | |
| | | |
| | | |
| | | | |
Users can be named null
|
| |/ /
|/| |
| | |
| | | |
First step on getting the authorisation stuff cleaned up. This is only for the login form, all other stuff is still where it is.
|
|/ /
| |
| |
| |
| | |
All classes that were previously \OC\Files\Storage\FooBar are now
\OCA\Files_External\Lib\Storage\FooBar
|
|\ \
| | |
| | | |
misc: Fix some typos
|
| | |
| | |
| | |
| | |
| | |
| | | |
Some of them were found by codespell.
Signed-off-by: Stefan Weil <sw@weilnetz.de>
|
|/ / |
|
| |
| |
| |
| | |
Add unit testing capabilities for templates
|
| |
| |
| |
| |
| |
| |
| |
| | |
The hook now calls the share manager that will call the responsible
shareProvider to do the proper cleanup.
* Unit tests added
Again nothing should change it is just to cleanup old code
|
|\ \
| | |
| | | |
Remove pre/post_addToGroup hooks for shares
|
| | |
| | |
| | |
| | |
| | | |
There is no need to perform the checks for unique targets on add to
group as we have to do this all when mounting the shares anyway.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Make lock ttl configurable
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
If we do not allow public upload we should limit the permissions on
links shares upon retrieval.
* Added unit test
* Allow fetching federated shares by token as well
|
|\ \ \
| |/ /
|/| | |
Migrate post_userDelete hook to share manager
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes the post_userDelete hook call the sharemanager. This will
cleanup to and from this user.
* All shares owned by this user
* All shares with this user (user)
* All custom group shares
* All link share initiated by this user (to avoid invisible link shares)
Unit tests are added for the defaultshare provider as well as the
federated share provider
|
| | |
| | |
| | |
| | |
| | |
| | | |
Fix also a small grammar issue.
Signed-off-by: Stefan Weil <sw@weilnetz.de>
|
|\ \ \
| | | |
| | | | |
Drop JS based acceptance tests - we have our behat based integration …
|
| | | |
| | | |
| | | |
| | | | |
which are activly maintained
|
|\ \ \ \
| | | | |
| | | | | |
Move OC/Core completely to PSR-4
|