Cloud/Files Bug
I was contacted today by a user who had created a folder called ‘GNU/Linux’ in the cloud and had come across a bug. I was able to reproduce the error described in the ddev environment (and also fix it by deleting the entry from the database).Bug:
If you enter a filename containing a ‘/’ for a new directory, a 404 error occurs immediately. It then becomes impossible to access the Cloud at all (always returns a 404). Only by deleting the row containing the filename from the ‘attach’ database table can the problem be resolved, allowing access to the Cloud once more.
Either this behaviour must be rectified somehow (I fear this may not be possible, as “/” is, after all, a path separator), or measures must be taken to prevent folder names (and perhaps also file names, e.g. when renaming) from containing a “/” (by removing it upon creation or refusing to create the folder/file).
The user will now probably have to contact the hub administrator and ask for the folder to be deleted from the database so that they can use their cloud again (
DELETE FROM attach WHERE filename = “GNU/Linux”;)