2
0
Fork
You've already forked cms
0

Context aware and customizable upload file naming #44

Open
opened 2025年03月06日 20:27:33 +01:00 by RickCogley · 1 comment
RickCogley commented 2025年03月06日 20:27:33 +01:00 (Migrated from github.com)
Copy link

Consider: upload image prep is a bit of a burden for users, asking them to follow naming conventions or to pre-optimize by compressing or resizing. We can help in Lume with the Picture plugin, and I'm wondering if the CMS could also be configurable to help.

When uploading in the context of a page, the page has fields so could the uploaded image be made to use those? For image1.png, rename like this using tokens:

{pageFilename}-image1-{time}.png
{pageId}-image1-{pageLang}-{time}.png

The recent addition of the ability to upload multiple files would necessitate a sequence suffix when a naming conflict arose from how a renaming rule was set, I believe.

There is a hidden benefit to this because it makes images in uploads easier to find later, when you're archiving a blog or tidying up.

Consider: upload image prep is a bit of a burden for users, asking them to follow naming conventions or to pre-optimize by compressing or resizing. We can help in Lume with the Picture plugin, and I'm wondering if the CMS could also be configurable to help. When uploading in the context of a page, the page has fields so could the uploaded image be made to use those? For image1.png, rename like this using tokens: ``` {pageFilename}-image1-{time}.png {pageId}-image1-{pageLang}-{time}.png ``` The recent addition of the ability to upload multiple files would necessitate a sequence suffix when a naming conflict arose from how a renaming rule was set, I believe. There is a hidden benefit to this because it makes images in uploads easier to find later, when you're archiving a blog or tidying up.
RickCogley commented 2025年03月06日 20:34:45 +01:00 (Migrated from github.com)
Copy link

Also, the ability to force-rename a file name to lowercase would reduce associated problems.

Also, the ability to force-rename a file name to lowercase would reduce associated problems.
Sign in to join this conversation.
No Branch/Tag specified
main
lumecms/outra-versión
lumecms/proba-2
v0.15.7
v0.15.6
v0.15.5
v0.15.4
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.16
v0.14.15
v0.14.14
v0.14.13
v0.14.12
v0.14.11
v0.14.10
v0.14.9
v0.14.8
v0.14.7
v0.14.6
v0.14.5
v0.14.4
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.0
v0.13.0-beta.1
v0.13.0-beta.0
v0.12.5
v0.12.4
v0.12.3
v0.12.2
v0.12.1
v0.12.0
v0.11.5
v0.11.4
v0.11.3
v0.11.2
v0.11.1
v0.11.0
v0.10.5
v0.10.4
v0.10.3
v0.10.2
v0.10.1
v0.10.0
v0.9.4
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.3
v0.8.2
v0.8.1
v0.8.0
v0.7.7
v0.7.6
v0.7.5
v0.7.4
v0.7.3
v0.7.2
v0.7.1
v0.7.0
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.10
v0.5.9
v0.5.8
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.3
v0.4.2
v0.4.1
v0.4.0
v0.3.12
v0.3.11
v0.3.10
v0.3.9
v0.3.8
v0.3.7
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.11
v0.2.10
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lume/cms#44
Reference in a new issue
lume/cms
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?