When typing a name for a new content type or a new view, its machine name is automatically generated as the user types. There is an "edit" link next to it, so that the machine name can be manually edited to be different from the human-readable name:
This "manual" mode for the machine name also kicks in when validation for a machine-name-enabled field fails (when the user leaves the field blank for example). The "Machine-readable name" field in these cases is being exposed, so that the user can free-type the machine name themselves:
When the "Machine-readable name" field is exposed, non-valid characters are allowed to be typed:
...only to throw validation errors when the form gets saved:
Describe the solution you'd like Have it so that as the user types in the machine name manually, the same javascript kicks in as when we are automatically creating the machine name for them. So:
- if the user types capital letters, they are converted to their respective lower-case ones.
- if the user types non-latin letter, they are converted to their respective phonetic replacement combos.
- if the user types symbols, they are either ignored, or replaced with an underscore.
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