first things first.
Thank you for your great work!
I’m a little bit confused.
I’m running NC9 for a customer on a Ubuntu-Server.
But the problem is a client or better any client.
I think its a design flaw in the client. But I let myself be instructed.
If I use a slash / in a filename the client is not able to upload this file.
Becase the / disturbs the url which contains off slashes.
The Client 2.2.4 on Windows and Mac show both an unspeecific error like “unknwon” error.
German: Beim Öffnen eines Ordners ist ein Fehler aufgetreten. Unbekannter Fehler
Nothing the in activity logs.
Only in the main Log (F12) I was able to fine the cause. The file was hidde deep inside some directories.
The Question is not what the problem is.
The Question is why does it need to happen this way?
I think there are two ways.
A) show the user an helpfull information. use the internal blacklist funktion. This way the information is shown in the activity log. This should be easy to do.
B) why not to encode the filename? mask the “bad” characters in each OS?
The same Problem should happen if I create a file with a backslash on mac and sync it to windows.