You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking at integrating this package into a CMS that we use for websites because we believe that this has more to offer than most solutions.
However, what we're struggling with is the ability to maintain the current upload structure and filenames. For example, we use the following structure:
Images: uploads/images/[date]/[filename]
Audio: uploads/audio/[date]/[filename]
Video: uploads/video/[date]/[filename]
Documents: uploads/documents/[date]/[filename]
Other: uploads/other/[date]/[filename]
Our files are also named, with their pixel size too (if edited):
Original: uploads/images/2025-04-07/image.jpg
Thumb: uploads/images/2025-04-07/image[300x300].jpg
Medium: uploads/images/2025-04-07/image[616x486].jpg (Width is set, but height is varied)
Large: uploads/images/2025-04-07/image[916x850].jpg (Width is set, but height is varied)
I do appreciate that this library is setup to handle things in a particular way, especially deleting and how it finds the "conversions".
Is there a way of maintaining our current setup with naming conventions?
After testing, and setting up a customPathGenerator it seems you can't remove the "collection" name from the file itself. Which again I appreciate you might not be able to because that is how this works.
I'm not ruling out migrating to match this setup, but I have to weigh up SEO impacts on such a change.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been looking at integrating this package into a CMS that we use for websites because we believe that this has more to offer than most solutions.
However, what we're struggling with is the ability to maintain the current upload structure and filenames. For example, we use the following structure:
Our files are also named, with their pixel size too (if edited):
Original: uploads/images/2025-04-07/image.jpg
Thumb: uploads/images/2025-04-07/image[300x300].jpg
Medium: uploads/images/2025-04-07/image[616x486].jpg (Width is set, but height is varied)
Large: uploads/images/2025-04-07/image[916x850].jpg (Width is set, but height is varied)
I do appreciate that this library is setup to handle things in a particular way, especially deleting and how it finds the "conversions".
Is there a way of maintaining our current setup with naming conventions?
After testing, and setting up a customPathGenerator it seems you can't remove the "collection" name from the file itself. Which again I appreciate you might not be able to because that is how this works.
I'm not ruling out migrating to match this setup, but I have to weigh up SEO impacts on such a change.
Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions