Hi, we have a folder with special permissions (on a Windows 2016 server) for the students that they can upload a file but cannot rename it once uploaded. So they drop of the file to the teacher folder and only the teacher can see it.
It was always working thru owncloud, but since I upgraded the server to 10.2 it stopped working.
The file is there but with a “.PART” extension, if I rename the file it is ok.
I restore the owncloud 10.0.10 and it is working.
It seem that the new version of owncloud (or the new php 7.2) changed the way it upload the files? Upload a .PART first then rename the files? And since the student cannot rename the file it stay has .PART?
It is working for all other folders but not this one.
The permissions on the folder are:
Applies to: This folder and subfolders
Read Extended Attributes
Does someone has an idea what changed?
Yes. The file is uploaded in chunks of 10 MB by default (?) and then reassembled and renamed.
You can try to disable chunked uploads. There is some info about how to do it in Disabling chunked file uploads
I expect the file to be uploaded directly, so there shouldn’t be a problem with the rename.
Does that mean you upgraded to PHP 7.2 with the new ownCloud ugprade? Which version did you upgrade from?
When you ‘downgrade’ ownCloud, do you also use the old PHP version again?
Are there any differences in the PHP configurations between the different PHP versions (make sure to check the right PHP configuration files, eg.
I already disabled chunked files, but it doesn’t work, it still downloading a .PART directly to the smb share (instead of a tmp).
I’ve updated Ubuntu to 19, maybe this is the problem I saw that owncloud support 18.
I didn’t downgrade owncloud, I just restored the VM. The PHP file is the same has before.
Anyway I will wait for a more recent appliance and change it then.
As far as I know the PHP version between Ubuntu 18.04 and 19.04 is the same: 7.2
So I think in this case we can rule out that it has anything to do wtih a PHP version upgrade.
So I assume your students use ownCloud to upload a file to this special folder, which is in fact an external storage with special permissions on NTFS which only allows creation but no modification.
I’m not sure how, if chunking is enabled, ownCloud puts the file back together. Does it put together a ‘.PART’-file which is then renamed or does put together to the file with the right file name straight away?
If the latter is the case I would assume you already have chunking disabled, so it would be worth trying to enable it again (if you can).
Otherwise I noticed in the release notes of the current ownCloud version 10.2.0 it says something about more granular permissions and a ‘File drop’ permission for guests on public links. Perhaps that would be an alternative way of implementing your workflow?
Hi, I tested a new upgrade of ownCloud (without updating Ubuntu) and I still have this problem.
I mounted the share on the console of the server with the same user and it is working.
I guess the new version of ownCloud don’t use the tmp folder to upload anymore? It just upload directly to the share folder, with a .PART, then (want to) rename the file which the user don’t have the permission of doing. So the file stay with the .PART extension.
Even a 10Kb file do this.
So nobody use this kind of “drop” folder for students??
I have a folder for each teachers (around 500) and the students groups has the special permission to their teachers folders.
Because of this I cannot upgrade.
I think we’re missing some information here. Can you answer the following questions one by one:
- How do you connect your external storage with ownCloud?
- What is your actual workflow (where do your students upload via the share directly or through ownCloud, if through ownCloud how is the share configured)?
- Which version (OS/PHP/ownCloud) worked?
- What do you upgrade?
- How do you upgrade?
- Why is ‘File Drop’ not an option for you?
- Can you provide a config report?
A configreport is functionality in the WebUI and the CLI to generate a JSON file of all the ownCloud settings.
You can find how to generate one in our documentation:
I guess the SMB storage is set up with a user that doesn’t have modify permissions on Windows filesystem level?
The mind boggling thing here is that it stops working with an upgrade, so something would have to change regarding the file upload handling to external storage between the ownCloud versions.
Would you perhaps able to provide a config report for both the working ownCloud setup and the one where it stops working?
Do you see any errors in the owncloud.log file at the end of the upload, that could be helpful?
I would recommend to set up a test instance with the new version where you can reproduce the error.