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

Etag isn't propagated to the root of the share owner if the file is uploaded to a group reshare #20714

Closed
jvillafanez opened this issue Nov 24, 2015 · 8 comments
Assignees
Milestone

Comments

@jvillafanez
Copy link
Member

Steps to reproduce

  1. User setup:
    • u1 without group
    • u2 and u3 inside group g1
    • u4 and u5 inside group g2
    • u6 and u7 inside group g3
  2. u1 creates folder /test
  3. u1 shares /test with groups g1 and g2
  4. u2 (member of g1) reshares /test with g3
  5. u6 (member of g3) uploads to /test/test_file.txt

Expected behaviour

Etag is propagated to all of the users

Actual behaviour

u1 doesn't change the etag of the root folder. The uploaded /test/test_file.txt can be seen as expected

Server configuration

Operating system: ubuntu 14.04

Web server: apache 2.4.7

Database: mysql

PHP version: 5.5.9

ownCloud version: 8.2.1

Updated from an older ownCloud or fresh install: fresh install

ownCloud log (data/owncloud.log)

Other than some locking errors that aren't affecting the outcome, nothing worthy

Related smashbox testing: owncloud/smashbox#137

@jvillafanez jvillafanez added this to the 8.2.2-current-maintenance milestone Nov 24, 2015
@rullzer
Copy link
Contributor

rullzer commented Nov 24, 2015

propegator fun! @icewind1991

@PVince81
Copy link
Contributor

proper gator 🐊

@icewind1991
Copy link
Contributor

Can't reproduce on master

Did you test this with #20439 merged?

@PVince81
Copy link
Contributor

@icewind1991 seems it was observed on 8.2.1

@icewind1991
Copy link
Contributor

Do we want to look into a separate fix for 8.2.x (no idea how much work that will take pre-9.0 etag propagation is a complex beast) or rely on #20439 and only have it fixed for 9.0?

@PVince81
Copy link
Contributor

PVince81 commented Dec 3, 2015

Yes, let's look into a 8.2 specific fix. Hopefully it won't be that complicated.

@icewind1991
Copy link
Contributor

Fix is here: #21044

@lock
Copy link

lock bot commented Aug 7, 2019

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.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 7, 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