Bug #61225
closed
Wrong upload error shown for /user_upload/
0%
Description
When I upload a file to /user_upload in fileadmin the upload works. Which means the file is on the harddisk in the correct directory.
But after the Upload Typo3 shows the error:
Uploaded file could not be moved! Write-permission problem in "/user_upload/"?
After that, the /user_upload directory cannot be browsed, because it shows:
Metadata can only be retrieved for indexed files.
This error only disappears if I delete the uploaded file from the harddisk.
Files
Updated by Markus Klein about 10 years ago
Did you check the permissions on the directory /user_upload?
Updated by Peter Buzanits about 10 years ago
Markus Klein wrote:
Did you check the permissions on the directory /user_upload?
It also happens when I set the permissions to 777.
Updated by Markus Klein about 10 years ago
Can you please modify
typo3/sysext/core/Classes/Utility/File/ExtendedFileUtility.php
and change line 949 from$this->writelog(1, 1, 100, 'Uploaded file could not be moved! Write-permission problem in "%s"?', array($targetFolderObject->getIdentifier()));
to$this->writelog(1, 1, 100, 'Uploaded file could not be moved! Write-permission problem in "%s"?', array($e->getMessage()));
and post the resulting error message here?
Updated by Peter Buzanits about 10 years ago
I made the change to ExtendedFileUtility.php and this is the resulting Error Message:
Uploaded file could not be moved! Write-permission problem in "Metadata can only be retrieved for indexed files."?Upload of file "DSC_1727_col_kl.JPG" failed!
Updated by Peter Buzanits about 10 years ago
- File exception.txt exception.txt added
I also serialized the exception object with print_r($e, true) and I add the (big) result as file attachment.
Updated by Peter Buzanits about 10 years ago
Just found out what the problem probably is!
I compared the database to a working installation and found out that the table "sys_file" is missing! Don't know how that happend. So this could be an issue with the installer.
I will try to install Typo3 on the same server again and check what happens...
Updated by Markus Klein about 10 years ago
- Status changed from New to Needs Feedback
- Priority changed from Must have to Should have
That explains the exception that the indexing of the file failed. ;-)
Updated by Alexander Opitz almost 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.