Consider Renaming files by the share receiver

[micbar]

Description

If a shared file is renamed by the sharee (share receiver) the sharee could not find the file searching for the new filename.

Steps to reproduce

1) Create "User01" and "User02" 2) Create file "good user experience.txt" with content "yes, for sure" as "User01" 3) run cron.php 4) Share file with "User02" 5) Log In as User02 6) Rename the file to "bad user experiance.txt" 7) Run cron.php 8) Search for "bad" -> no results

Cause of the problem

• The file is indexed in with the filename from oc_filecache
• Both Users are allowed to access the data for this file
• The new name, that User02 has set, is saved in oc_share and not present in the search index

[micbar]

@butonic @patrickjahns found this already existing issue from last year.

[davitol]

@micbar Following the Steps to reproduce you posted in OP i was not able to reproduce the issue. Could you please retest if possible?

8\. Search for "bad" -> no results

The last step refers to user2 no?

[micbar]

@davitol Can you confirm, that your file was in a subfolder and not visible to the screen / view from where you searched?

[davitol]

@micbar No, it was in Home path, file visible to the view where I searched. I did not see if the issue was only related to files in subfolders...

[davitol]

file was in a subfolder and not visible to the screen / view from where you searched

With these conditions the issue is reproducible. Sorry for the noise

[davitol]

What it also happens is that file appears in the search looking for the old and the new name:

[micbar]

@davitol there is a difference in the search behavior between a filename on the current view and a filename in a folder.

1) The file on the same page is found by core js 2) The file somewhere else is found by elasticsearch, see "X search results in another folder"

This could lead to unexpected behavior.

[micbar]

unassigning.