Bug #56127
closed
Images not processed in backend context if special chars in path
Added by Philipp Wrann almost 11 years ago.
Updated over 9 years ago.
Category:
File Abstraction Layer (FAL)
Description
The filelist fails in creating processed images... The processed file exists on hard drive but has 0 bytes. Also the permissions are not set as configured in the install tool, they are allways 640 instead of the configured value for new files.
recognized if a image is in a subdirectory which has special characters like ä|ö|ü in its name.
tested in 2 environments, both LAMP PHP 5.3 / TYPO3 6.2 / Imagemagick enabled
Files
Hi Philipp,
Do you have "[SYS][UTF8filesystem] " set in the install tool?
Do you also have "[SYS][systemLocale]" set to correct (utf-8 aware) locale in the install tool?
You can verify systemlocale by going to install tool to the "System environment" tab. Recently there was new check added just for checking issues similar to the one reported by you. Make sure, you have the most recent 6.2 version from git.
Please let me know what you find out.
No, didnt have it "on", checked the option but still the same.
In my opinnion utf8 has to be the default setting for FS and DB in all areas.
Set systenLocale to de_DE.UTF-8, now it seems to work.
This could be a common problem for everybody, maybe display missing configurations and examples based on backend language somewhere at the home-screen would be of great help...
I stumbled over some other problem today.
When a folder contains whitespaces i get a FolderDoesNotExist Exception.
This is now the second hoster the problem occures. One time on a selfmanaged rootserver i think i configured right, the other one is hosted at domainfactory on a managed server.
Each installation has problems with special characters.
I dont know if its a host configurationproblem or its related to TYPO3... But please take a look at it.
Ah forgot:
The exception is thrown when checking for a file...
- Status changed from New to Needs Feedback
- Priority changed from Must have to Should have
Philipp Wrann wrote:
I stumbled over some other problem today.
When a folder contains whitespaces i get a FolderDoesNotExist Exception.
This is now the second hoster the problem occures. One time on a selfmanaged rootserver i think i configured right, the other one is hosted at domainfactory on a managed server.
Each installation has problems with special characters.
I dont know if its a host configurationproblem or its related to TYPO3... But please take a look at it.
I could neither reproduce the umlaut issue nor the whitespace character problem with recent Git master.
Can you please provide some additional information on the used system? Best would be the full PHP info output (phpinfo()) - you can send it via mail to oliver@typo3.org as well, to prevent your path and possibly domain names flying around in the public... Thanks in advance!
- Status changed from Needs Feedback to Accepted
Okay, I could reproduce the whitespace character problem on renaming a folder...
Oliver what behaviour could you reproduce? When you rename a folder with a space in the name the space is replaced by a underscore. This shouldn't lead to problems.
- Status changed from Accepted to Needs Feedback
- Target version deleted (
6.2.0)
- Is Regression changed from Yes to No
Is this still an issue with 6.2?
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 