search

nextcloud / server

☁️ Nextcloud server, a safe home for all your data
https://nextcloud.com
GNU Affero General Public License v3.0
27.16k stars 4.03k forks source link

Renaming folder doesn't sync to other users #2063

Open apodosenin opened 7 years ago

apodosenin commented 7 years ago
### 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) ... ```
Bolkarr commented 4 years ago

+1 I am using nextcloud to share pictures with the family members as read only (I am the sole controller of the files to prevent deletion/change etc). I create the folders and dump the related pictures in them, when I have time, I go back and rename the folders (for example adding the name of the event, like Jennies birthday etc.). However existing behavior makes it impossible to push the changes to other users, they still see the folders as they were first created, and this is causing lots of problems. Please at least give this as an option. I would like to keep "every" file/folder that are shared same regardless of which user it is. I believe if there is an existing name conflict, app should notify the user and allow them to change their local folder/files, since shared stuff should take priority (because it is used my many).

secure11 commented 4 years ago

I started this thread long ago. Still really need this functionality. Your product is superior in so many other ways; however it is a showstopper for us without this functionality.

agentlibre commented 4 years ago

I read it too as an issue rather than a feature. I'm promoting FOSS to layperson users within my organization and this naming desync creates a lot of confusion and mistrust. I love NextCloud and would like to contribute further to its development to the best of my abilities; yet, this renaming issue is a hard blow for proper collaborative work.

Another note: can't tell whether it is related or not, but it seems I cannot delete a "main" folder for the others without having it re-appear on their own web interface...

Isn't there some sort of ownership's right attached to a folder you create? This could perhaps be a first lead to solve the issue.

madhums commented 4 years ago

It's not intuitive to ask each user to rename a folder or to get everyone on the same page for a folder name, especially if you are working in a big team with thousands of people. Could you please fix this?

jospoortvliet commented 4 years ago

I think that there are two cases here.

Scenario one: shared workspace for a team or entire organization You want to share a folder with a team because it is to be a shared resource, a place where the team works in and with for an extended time. Say a Marketing folder, or the Engineering folder. You share because you are the manager or just put in charge of creating and distributing this resource. You might be an admin or sub-admin. As potentially many people have access to the shared resource, to keep everyone 'on the same page' it is easiest if the name stays under your control. You are essentially enforcing a way of working and organizing to facilitate smooth collaboration in a larger group. This is clearly what @madhums is talking about at https://github.com/nextcloud/server/issues/2063#issuecomment-591409114

Scenario two: a one-off share You uploaded a few docs you are working on with one or two colleagues. This is kind of a scratch space, something you work on for a week or maybe two. You share because you just happened to be the one who gathered or created the content, not because you have a special role, most certainly you're not an admin. As only a few people have access, it's best if the resource fits in everybody's own workflow. They can move the folder or, yes, even give it another name - if that's easier for them to remember what it was about. It is a temporary resource so your priority is to lower the barrier for the few ppl working on this and let them work how they prefer. This was described by https://github.com/nextcloud/server/issues/2063#issuecomment-412939476

So, I think we actually have a 'perfect' solution for this and should close this issue. But first I want to point out that this isn't much of a private user issue - we cover scenario 2 (which is a typical SMB/private user case) just fine, with the default.

If you're a business and you had a subscription, as part of onboarding, you would have discussed how you work with us. And we'd have told you what the best way of dealing with such issues is: create a groupfolder. That does EXACTLY what you need, with a few added bonusses: people can't unshare it, you can set fine grained access control lists and more. If you work with 'thousands of people' like @madhums does then yes, this is your solution, don't just share a folder with everyone because that will get you in trouble.

Consider this free advice - and consider the loss in productivity your thousands of people experienced because you didn't simply discuss this with the right experts earlier on in the setup of your instance.

GillesMocellin commented 4 years ago

Hi @jospoortvliet,

Last time I checked, groupfolders do not work with encryption (server side). That's a blocker for some enterprises.

nickvergessen commented 4 years ago

Since groupfolders can not be external storages atm, the argument of serverside encryption is invalid as per our explanation (warning box on https://docs.nextcloud.com/server/18/admin_manual/configuration_files/encryption_configuration.html )

GillesMocellin commented 4 years ago

Ok, another downside of groupfolders. So we should have a better way to share files with external storage and encryption. My use case needs scalability and big storage, so I aim to use external object storage via S3.

joeltheukranian commented 4 years ago

My client needs the rename to work as well. Each user does not want a name other than the original name given. Most of the people using it are non-techies, so having "labels" and names will likely confuse them. Please advise on your plan.

They are looking seriously into paid support. Because we will need it.

My suggestion would be an addon that forces rename across the board to all users. Or a configuration change (ofcourse) "force_rename_propagation = true".

Excpt0r commented 3 years ago

@jospoortvliet Thanks for the free advice.

Just my free feedback, no complaint. I like OSS to succeed.

handkerchief333 commented 1 year ago

Is there any progress on this issue? I face the same situation in 25.0.3

EddyLB commented 1 year ago

More detrimental is that the share is also lost if the user having shared the folder renames it afterwards. A really big issue.

solracsf commented 1 year ago

To be clear here, ATM, the options are:

If you're using GroupFolders, i could also recommend Workspace (requires GroupFolders): https://github.com/arawa/workspace

kaffeeringe commented 2 months ago

I spent half a day today trying to find out why a share can have a different name for me than for a colleague. I then came across this ancient thread and was initially horrified that this was supposed to be an intentional behavior of Nextcloud.

However, it can be practical if people set up their Nextcloud in the way that suits them best.

But you should really think about how organizations should work with Nextcloud. Creating a functional account that creates and shares all shared resources is an okay solution: Folders, address book, calendar, etc.

It is inconsistent if you have to set up shared folders via an external app, but have to create and share other resources via a functional account.

It would actually make sense if an admin could create a new workgroup including resources and assign the necessary accounts to this workgroup. Currently, you have to do all this manually: https://kaffeeringe.de/2024/07/02/projektmanagement-mit-nextcloud/

timirons commented 1 month ago

This is still a major problem for us. Maybe we could have a setting to fix folder names as it is a nightmare. All we can do is unshare and reshare. I can understand the two use cases, but for corporate file structures, it doesn't work very well at all.