This is basically a request to integrate some of the functionality of File (Field) Paths into core. Here's the file field configuration page, once the module is enabled:
The redirect and active/retractive update bit can be left for contrib (or to be solved by #854); the transliteration bit is already implemented in Backdrop (admin/config/media/file-system); the redirect can be left for a separate issue (or contrib); what I find a valuable feature though is the ability to use tokens for file names and file paths. The later is what this issue here is about.
Original request
There is a feature request for this filed in the File (Field) Paths module issue queue that is marked as "closed/fixed". It states that Entity API exposes this as a token (I think it's the Entity Token sub-module actually):
Looking at our token browser though, the deepest I could get to is [node:field_image].
Recent comments
You can edit images and load them back to the same folder with the same name and extension, this will not create a problem. Replace directly in the file system, without the use of CMS, for CMS...
Image manipulation on server?
I was under the impression you could not do that - don't know where I got that idea from... thought it had to do with the way Backdrop manages image files.
Image manipulation on server?
I think given the warning on the source site: At this time, if your new project can afford to require PHP 5.5+, which it should, please use PHP's native password_hash() /...
July 31, 2025