Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When PHP fails due to unicode path issue, terminate application immediately #74

Closed
GoogleCodeExporter opened this issue Aug 28, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Aug 28, 2015

When application is started from a path that contains unicode characters, then you will see a "No input file specified." message in the browser window. Example location on XP:

C:\Documents and Settings\Unicode ąć\My Documents\Downloads\

Where "Unicode ąć" is the user's account name on Windows XP.

The solution would be to check the content of the initial web page during application startup, if it equals to "No input file specified" then application should be terminated immediately and a message should be displayed to user, something like:

Application has detected that it has been placed in a location on your hard drive that contains unicode special characters (%DISPLAY_PATH_HERE%). Due to some constraints this is not allowed. Application will terminate immediately.

This kind of problem occurs when your Windows account name contains non-standard characters. The solution is to put application directory in a location that contains only standard ASCII characters, put it to "C:" or to "C:\Program Files". Application must have permission to write files in that location.

Original issue reported on code.google.com by czarek.t...@gmail.com on 1 Feb 2014 at 1:54

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Aug 28, 2015

Fixed in revision d56e9a3.

See the attached image to see how does the error message displayed to user look like.

On Win XP after clicking that dialog, some other error appears ("could not write to memory at location.."), but fixing that isn't that important I think, as this is a special case when application exits and user already knows there is something wrong going on. The second error message doesn't occur on Win7.

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants