Copy of a folder from a read-only share to a write share : files stay read-only

ℹ️ Support
1

I am setting up the use of Nextcloud for file sharing thru web browser and local client. One of the features I intend to create is to allow users to clone a folder and its subfolders from a read-only share to their home folder, where they can write.

The read-only share is hosting templates and the such : is read-only for most users, and write for the guys responsible for managing the templates.

The issue I am facing is that the copied files can’t be modified either from the web interface nor the local sync client. And when I look at the file properties in the Windows explorer, I see that the “read-only” file system attribute is set on the copied files in the home folder. If I unset the attribute, I can modify the file in the web interface and in the synced folder.

I don’t have administrative access to the host, so I can’t use a trick to copy the files another way than using the copy files feature of the web interface.

I tried to copy the file from the web interface or from the synced local copy and the result is the same (it is actually normal behavior for a local copy in an NTFS file system).

Do you experience the same issue, and is there a solution or workaround ?

2

I made a test on another Nextcloud instance and didn’t encounter this issue. So it is specific to the first instance. How weird…

3

What are the versions of your Nextcloud Servers?
We’ve the same behaviour on 4 Nextclouds v31 instances!

4

The Nextcloud server having the issue is version 29.0.11 and the one not having the issue is version 28.0.9.

I will soon upgrade the second one, will be able to tell if the version is involved.

5

Hi, I’m also facing this issue with v29.0.11, I tried to upgrade to v29.0.14, v30.0.8 and v31.0.2 but the bug is present in all of them…

6

FYI I reported the bug on Github issues : [Bug]: Can't edit/delete files copied from read-only shared folders · Issue #51846 · nextcloud/server · GitHub

1 Like
7

@chapa , thanks for creating the bug report.

I don’t have shell access to the nextcloud instance having the problem, and could not reproduce it on another one ; so I can’t check the filesystem directly.
Did you check the file permissions at the filesystem level for the affected files ? Does the apache user own all the files ? Are they set as read-only after being copied or something ?

Also, on your affected server, is the option preventing re-sharing activated ?

Guy

8

I tried this on every last version of v29, v30 and v31 with this basic docker compose file :

services:
  mysql:
    image: mariadb:10.2
    environment:
      - MYSQL_ROOT_PASSWORD=root
      - MYSQL_PASSWORD=nextcloud
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  nextcloud:
    image: nextcloud:29.0.16-apache
    depends_on:
      - mysql
    ports:
      - '8080:80'

All the files are owned by the apache user as they should, with regular permissions. And I didn’t change any option, so by default re-sharing is enabled.

It seems that the bug has been acknowledged, someone from the Nextcloud organization created a MR to add an integration test here: Add integration tests for deleting a file copied from a share by danxuliu · Pull Request #52970 · nextcloud/server · GitHub. It still needs to be fixed though.