| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Link shares always allowed deletion, however internally the permissions
were stored as 7 which lacked delete permissions. This created an
inconsistency in the Webdav permissions.
This fix makes sure we include delete permissions in the share
permissions, which now become 15.
In case a client is still passing 7 for legacy reasons, it gets
converted automatically to 15.
|
| | |
|
| | |
|
|\| |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
in case of federated re-shares the owner can be a remote user.
Therefore we can't always use to owner to access the local file
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The last sharing hook to be moved over.
* Added unit tests
* Removed old tests that relied on old behaviour
* Removed old hooks.php
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|\
| |
| | |
re-try to send unshare notification if remote server is not available
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
|
| |
This was added to the factory for legacy reasons when converting from
old to new sharing code. It is not used anymore so can be deleted. Which
means we no longer expose internal types.
|
|
|
|
|
|
| |
Fixes #23337
We only allow the id to be set once!
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #23536
The new sharing code is much stricter in checking permissions. However
for non moveable mounts the permissions UPDATE+DELETE are not reported
on the mount point.
This is just a quick fix.
* Updated unit tests
|
|
|
|
|
| |
This was used when we did not have lazy shares yet. Now that we no
longer support legacy shares this can go.
|
|
|
|
|
|
|
|
|
| |
In 9.0 we converted the old shares to the new shares. So for 9.1 we can
savely remove the fallback code.
This code was required when there was no initiator set.
* Fixed unit tests
|
|
|
|
| |
* Fix tests
|
| |
|
|
|