Skip to content
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

Versions not created when updated via webdav #16130

Closed
rullzer opened this issue May 6, 2015 · 10 comments
Closed

Versions not created when updated via webdav #16130

rullzer opened this issue May 6, 2015 · 10 comments

Comments

@rullzer
Copy link
Contributor

rullzer commented May 6, 2015

When updating a file via webdav there is no version created. So basically if the sync client is used no version history.

Command used:

curl -X PUT --header "Content-Type:application/octet-stream" --data-binary @foo.txt http://user:pass@localhost/owncloud/remote.php/webdav/foo.txt

Of course with modifications to the data file.
The file is actually updated. But no new version is added.

I assume it is a bug. But could be that is just not yet properly implemented.

@rullzer rullzer added this to the 8.1-current milestone May 6, 2015
@karlitschek
Copy link
Contributor

There must be something wrong

@PVince81
Copy link
Contributor

This used to work => regression

@PVince81
Copy link
Contributor

@rullzer have you done any bisect before ?

@PVince81
Copy link
Contributor

It could be related to the "view" bypass implemented in the sabre file class which works directly on the storage. But AFAIK it should still manually trigger the hooks after putting the file, which would then trigger the versions code.

Needs further research.

@PVince81
Copy link
Contributor

I'll bisect this

@PVince81 PVince81 self-assigned this May 12, 2015
@PVince81
Copy link
Contributor

Regression introduced by #12006 from @icewind1991 where we work directly on the storage. Maybe for some reason hooks and stuff do not get triggered properly.

I'll try and debug this.

@PVince81
Copy link
Contributor

I see that hooks are triggered properly, they do reach the trashbin and sharing propagator. But somehow they don't reach the versions code, maybe the hook wasn't registered properly in this situation.

@PVince81
Copy link
Contributor

@icewind1991 we seem to be missing the pre-hooks. Only post hooks are triggered. Was this on purpose or just an omission ?

We probably need to trigger the "create", "update" and "write" hooks too. Not sure when. Need to check when they were triggered in the "old" version.

@PVince81
Copy link
Contributor

PR here: #16292

@nickvergessen
Copy link
Contributor

PR merged

@lock lock bot locked as resolved and limited conversation to collaborators Aug 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants