When accessing any file with a non Latin characters in its name I get a 404. In the explorer the files are shown correctly with their original unicode name. SSH and using ‘ls’ shows the file names as ‘???’ but it could be the console.
I am running Local on Windows 10 64 bit. Everything else seems to work.
Hi @ialhashim,
Sorry for the trouble!
Do you have “Faster Docker Volumes” enabled under Preferences » Advanced? If so, that may be causing the issue.
It was enabled. I turned it off but the problem is still there. I think it should be easy to replicate. Upload some media file with the name ‘تجربة.jpg’ (test.jpg). Then visit that file directly /wp-content/uploads/2017/07/تجربة.jpg. I get a 404. All other files and links are OK. (this is under Windows 10 home 64bit).
Update: actually uploading a file with unicode works but this new uploaded file on the system is named as weird characters (تجربة). My broken files are imported using a script from an existing site so on the system they are correct but the server can’t serve them with their real names. So there is an issue with Unicode naming.
Hi @ialhashim,
Thanks for the details!
Now that you’ve disabled Faster Docker Volumes, can you try clicking on the menu in the top-left of Local’s window and then going to “Restart Local’s Machine”?
That should reset the VirtualBox mounts and may fix the unicode issue.
By the way, what version of Local are you running? You can see by going to Programs & Features in the Windows Control Panel.
It seems it is fixed now. I think I tried restarting before but it didn’t work at first. But now after restarting the system it self the problematic links seem to work OK (not sure if thats related). Its probably the Faster Docker Volumes feature.
In any case. Thanks Clay! Maybe a bug report or note of this should be added for the future?