Renaming folder doesn't sync to other users

[apodosenin]

Steps to reproduce

1. Rename shared folder via Web interface
2. Sync folder with other user
3. Second user doesn't see new folder name

Expected behaviour

All users should see the same new folder name

Actual behaviour

Every user got his own folder name

Server configuration

Operating system: CentOS 7

**Web server: Apache/2.4.6 (CentOS)

**Database: mysql 5.5.38

**PHP version: 5.5.38

**Nextcloud version:10.0.1 (stable)

**Updated from an older Nextcloud/ownCloud or fresh install:updated from old ownCloud

Where did you install Nextcloud from:

Signing status:

Signing status

Login as admin user into your Nextcloud and access 
http://example.com/index.php/settings/integrity/failed 
paste the results here.

List of activated apps:

App list

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

The content of config/config.php:

Config report

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or 

Insert your config.php content here
(Without the database password, passwordsalt and secret)

Are you using external storage, if yes which one: local/smb/sftp/...

Are you using encryption: yes/no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...

LDAP configuration (delete this part if not used)

LDAP config

With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your Nextcloud installation folder

Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';


Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.

Client configuration

Browser:

Operating system:

Logs

Web server error log

Web server error log

``` Insert your webserver log here ```

Nextcloud log (data/nextcloud.log)

Nextcloud log

``` Insert your Nextcloud log here ```

Browser log

Browser log

``` Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...

</details>

[nickvergessen]

This is actually the expected behaviour, because the name might be different for each user and the users can rename the folder on their end.

[apodosenin]

Ok, not very good for centrally managed shared folders. Perhaps I'm not using your product in correct way. Any options to change this behaviour?
I've got another issue, if someone is editing file and other user renames it at the same time than file is duplicated after first user saves changes. Looks like this is by design too. Am I correct?

[secure11]

Commenting on this as for a centrally managed share folders/file system, if User 1 renames a file, ALL users should see it as renamed. Not following this behavior would be a big show stopper for any company thinking of migrating from sharepoint or dropbox to NextCloud? If two users are trying to make changes to 1 file and 1 user renames (not copies) it, both users are now working on different documents, and the other user doesn't even see (in the web or a synced version) the NEW file name??? What use case in a shared environment are you thinking the users should be able to have the same files/folders only give them different names without other users seeing the changed names? I can't even think of a use case where that is helpful, and doesn't end in a bad situation of identical files with different names not seen by all users who supposedly have access to the file(s)?

[JaredBoone]

Please consider reopening this. In my opinion, it is a valid bug. A shared file or folder that is renamed should still be properly shared.

[nickvergessen]

@secure11 you seem to misunderstand. Only the most outer folder you shared with someone is not renamed.

Example:

1. UserA shares level1 with UserB
2. UserB already has a folder level1
3. UserB sees their level1 and level1 (2) from UserA
4. UserA renames level1/level2/level3 to level1/level2/levelC
5. UserB will see this rename and have the file level1 (2)/level2/levelC
6. UserA renames level1 to levelA
7. UserB will still see the files in level1 (2)

The problem is that UserB could rename the level1 (2) at any point (e.g. to level1 (UserA)) at which point we shouldn't automatically rename the stuff any more.

A shared file or folder that is renamed should still be properly shared.

That is also a misunderstanding. Renaming a file does not remove or corrupt shares.

[JaredBoone]

@nickvergessen I don't mean that the share is removed or corrupted. I mean that if UserA shares a file1.jpeg with UserB, then UserA renames the file to file1.jpg then the file rename does not propagate to UserB. In the specific case reported to me by a user, he shared a file with a large number of users then realized that the file extension was wrong and wanted to correct it, but the new filename did not propagate to the other users. To work around this he renamed the file and then unshared and reshared it with each of the users. I got the impression from the user that he found this process inconvenient. Perhaps it's worth considering a way to make this more convenient? Thanks!

[nickvergessen]

I guess it makes some sense. Maybe @jancborchardt can comment on it.
Maybe we could/should rename mounts that use the same name or same name (%d)

[kjantin]

I am also configuring NextCloud to be used as a centrally managed share folders/file system and am running into the same kinds of issues shared in this thread. It would be ideal if a file that is renamed, is then renamed for all other users it is shared with.

[secure11]

Was this addressed by chance in the nextcloud 12 release? Seems to me this is a show stopper for many users and organizations?

[jancborchardt]

What are your takes here @karlitschek @schiessle @nickvergessen?

If I remember correctly we deliberately chose this path because lots of people mentioned they wanted to use their own ordering.

If however most other solutions do it in the way as described here, and our way results in confusion, we should adjust it. :)

[secure11]

For comparison, file/subdirectory synchronization in seafile and pydio work as we have described here. Also with Dropbox and office365. I used to use owncloud way back when and I don't recall this behavior so that is why I thought it was a bug in nextcloud?