Allow slashes in filenames

[PatrikKozak]

Being that most blob storage "folders" are really just files with slashes in them, might consider ability to upload files that contain slashes in their filenames so that they are uploaded to "folders".

The problem is, we use the sanitize-filename package which automatically removes slashes from filenames - so we should figure out a way to either allow slashes specifically or have an option to opt out of filename sanitization.

[mrobst]

100% - I was just about to raise a discussion about this having been fighting for a couple of days to get Payload to behave the way I want it to....... I think this might be a fairly easy answer.

Example use case:

• Multiple users with accounts on payload uploading images for processing.
• Image storage on any major cloud service.
• Users want to get their image back (download) later with the same filename so they can match the files up again.
• Image uploads for the same user should overwrite existing ones

Previous solution (not on Payload):

• Prefix all uploads for a user with their account id (unique) and "/" which creates a virtual folder in cloud storage
• 12345/image1.jpg
• 34567/image1.jpg
• Above example is for two different user accounts - all works fine

Payload currently doesn't allow "/" in the filename and expects all filenames to be unique across the whole application which is enforced by a unique index on filename in MongoDB which is automatically added on startup.

There is a way to manipulate the prefix on the cloud storage plugin to be dynamically named which means that you can write files to folders in cloud storage via upload field but as this is the prefix it doesn't change the filename. Payload checks for the file existence when image1.jpg is uploaded for the second user and doesn't take the prefix into account. The file is saved into the second folder but when MongoDB is updated it throws a unique error on the filename as it sees 2 "image1.jpg" filenames.

Allowing "/" in the filename would mean that the full name is stored in MongoDB and the unique index would still be valid.

At the moment I have to avoid using the upload enabled collections on Payload and just store URLs to storage as text which isn't ideal :-(

@PatrikKozak did you find any workaround? Can I influence the MongoDB index to use prefix and filename fields together?

References:
Hacking the prefix for folders...
https://discord.com/channels/967097582721572934/1184466437331488839/1204564297515012118

Uniqueness & santization (I want to avoid this!)
#1153 (comment)

Folder view- this might be part of the solution
#1961

[wkentdag]

I stumbled across this issue while migrating a set of Wordpress uploads to payload. The WP URL pattern /yyyy/mm/dd/<filename> gets flattened to /yyyymmdd<filename>, which breaks any existing asset URL. The workarounds mentioned in #1153 don't help in this case since the / chars ultimately get stripped here.

I wound up using some Next js middleware hackery to mostly sidestep this limitation. But IMO a cleaner solution would be to expose a sanitizeFilenameOptions config option where consumers can pass their own options directly to sanitize-filename. How does that sound?

[mrobst]

If I understand the santizeFilenameOptions correctly you can pass in a restricted character and define what to get back in that instance.... so ("/" -> "/") would probably solve the use case for cloud storage with virtual folders. The challenge is how to get the options exposed to payload.config.ts !