-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not wrap storage of owner anymore #24249
Comments
I did not try with the workflow app yet. But probabaly it goes wrong in https://github.com/owncloud/core/blob/master/apps/files_sharing/lib/sharedstorage.php#L84 Because that is where we get the storage that the jail wraps... |
When running a debug session... I do see the storage wrapper. But things go wrong when we try to run the plugin. This happens because the wrong cache is probabaly fetched there... I'll look into a bit more detail tomorrow. |
Could you try again with master. |
Mmm so it seems the tag is not set using the webUI but when doing the PUT via webdav all works fine... |
Fixes #24249 When a storage wrapper registeres itself before the FS is initialized this can create problems.
PR in #24280 |
@nickvergessen try not applying the storage wrapper in app.php directly but instead in the filesystem |
Right, that fixes the issue on plain master. So we should make sure that all apps use that instead of registering in plain app.php? |
Afaik all (our own) apps do it like that |
Well all our EE apps don't :P |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Since some day in the last week, I can not wrap non-shared-storages anymore.
Steps to reproduce
Expected behaviour
Tag is added
Actual behaviour
Tag is not added
Debugging
It works when you check out cdcabbd which is the last merge commit before: #23919
So I checked the storages and it looks like the sourceStorage inside the SharedStorage is created without being wrapped. I also checked with @schiesbn sitting next to me and there was never a try to wrap that storage.
Please help @rullzer @icewind1991
The text was updated successfully, but these errors were encountered: