-
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
Doubled folders when receiving shares through two groups #24575
Comments
Are you using different permissions ? If the permissions are the same, there is an algo that will merge the two folders. |
@PVince81 Yes, the permissions are identical. |
Hmm, then it could be a regression |
I most likely broke it then. |
@rullzer any update ? |
@rullzer can you fix it then ? |
Fixes #24575 Note that this is a very limited solution and eventually we want smarter merging!
PR incomming... but I actually don't know why this grouping isn't happening properly on 9.0 since I did not touch the mountpoint stuff then... |
The PR in question is here #25113 |
Fixes #24575 Note that this is a very limited solution and eventually we want smarter merging!
The problem happened when I upgrade from 9.0.2 to 9.0.3,It does not exist in my 9.0.2. |
what can / should I do in the meantime safely until the patch is availble with build 9.0.4?
PLEA: In both cases, the provided update should correct all wrong data (so that the many users of our instance don't have to waste additional time to get a cleanup of their directory/share structure) |
|
|
Fixes #24575 Note that this is a very limited solution and eventually we want smarter merging!
Just to clarify, now using this ticket to track any kind of "folder shared through multiple ways to the same user" resulting in the "recipient sees the folders multiple times" issue. |
|
Hi I ran into another issue, I applied the temporary fix for the sharing issue but now my owncloud doesn't want to sync with my mobile devices(Webdav or mobile app). Gives a HTTP error... can you please advise? |
* Group shares with same source and target Fixes #24575 Note that this is a very limited solution and eventually we want smarter merging! * Add integration tests for merging received shares * Improved share grouping readability + fixed test * Add repair step for unmerged shares (WIP) * Added more tests for sharing's MountProvider * Group incoming shares for resharing in JS * Adjust repair version check for unmerged shares * Fix RepairUnmergedShares to not skip valid repair cases The repair step was a bit overeager to skip repairing so it missed the case where a group share exists without subshares but with an additional direct user share. * Add integration tests for double shares with rename in between * Make share target consistent when grouping group share with user share In some situations, a group share is created before a user share, and the recipient renamed the received share before the latter is created. In this situation, the "file_target" was already modified and the second created share must align to the already renamed share. To achieve this, the MountProvider now groups only by "item_source" value and sorts by share time. This makes it so that the least recent share is selected as super-share and its "file_target" value is then adjusted in all grouped shares. This fixes the issue where this situation would have different "file_target" values resulting in two shared folders appearing instead of one.
@SMITR1 which ownCloud version do you have and which exact fix did you apply ? Depending on your ownCloud version, the fix is different. It is likely that you applied an incomplete fix. |
The PR is ready for testing: #25543 Please help testing if you have a test system. (don't do it on a productive system as it increases the version) To test:
|
Regarding the workaround while waiting for 9.0.5: you can safely delete the duplicates. The repair routine will still be able to figure out what to do. |
Fix will be in 9.0.5 and 9.1.1. |
Great, Tks a lot! On Aug 16, 2016, at 7:50 PM, Vincent Petry <notifications@github.com mailto:notifications@github.com> wrote: — |
You can help testing with the 9.0.5 RC1: http://download.owncloud.org/community/testing/owncloud-9.0.5RC1.tar.bz2 |
Sorry to reopen this, but I am still facing this problem on OC 9.1.2 (stable). Any ideas? |
@tavinus please make a new ticket and post reproduction steps and details about the sharing scenario. Use the issue template for that: https://raw.githubusercontent.com/owncloud/core/master/.github/issue_template.md |
I can still reproduce this problem in 9.1.4.2. This issue needs to be reopened. |
@craftyInstigator please make a new ticket and post reproduction steps and details about the sharing scenario. Use the issue template for that: https://raw.githubusercontent.com/owncloud/core/master/.github/issue_template.md. Most important is to know what exact sharing scenario you are using and the order in which the shares were created as it might affect the outcome. There is one known issue: #25564, please check if it matches your scenario exactly. |
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. |
Steps to reproduce
Expected behaviour
User U will have folder F in his files.
Actual behaviour
User U has folder F two times in his files (one is named "F (2)").
Server configuration
Operating system: Debian 8.0
Web server: Apache 2.0
Database: MySQL
PHP version: 5.6.20
ownCloud version: 9.0.2
Updated from an older ownCloud or fresh install: fresh install
Where did you install ownCloud from: via official aptitude repo
Signing status (ownCloud 9.0 and above): No errors have been found.
List of activated apps:
The content of config/config.php:
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
The text was updated successfully, but these errors were encountered: