Open xannyxs opened 2 weeks ago
Thanks Xander for doing this, great job. It is also important to (if you know who) assign it to someone from the beginning, also select a project where this belongs to.
Adding screenshots to the issue is also helpful. Once I have access to the repo I will edit the templates and stuff to make space for this kind of things.
Again, thanks for the effort.
Current Issue: When a user uploads an image named "anImage.png" and another user subsequently uploads a different image with the same name, the system does not upload the new image. Instead, it uses the image uploaded by the first user.
Proposed Solution: To avoid this conflict, we should use a unique identifier, such as the session or stage ID, instead of relying on
file.name
.Challenges: We need a strategy to handle legacy images that are currently identified by their file names.
Steps to Reproduce:
Expected Behaviour: Each image upload should be uniquely identified to avoid conflicts, ensuring that different images with the same file name do not overwrite each other.
Additional Notes: