Make sluggification visible, customizable, and fail-safe
Default sluggification is simplistic, relying on a title field and performing no inference whatsoever. **With no field named "title", entries currently fail to save.** The ideal fix is to simply make slugs editable in the editor UI. Considerations: * Slug editing can be switched off through config * If slug editing is switched off, each collection config must be validated on CMS load to ensure a slug can be derived * Prepopulate with the same best guess or configured slug template result that we currently use * Only valid characters may be entered in the slug field * Slugs and filenames are not always the same, so it should be possible to provide them separately somehow (see [comment](https://github.com/netlify/netlify-cms/issues/445#issuecomment-377425752) below for example)
Posted by erquhart on Jun 6, 2017, 9:14 PM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
- Feature Request: Auto-resume CLI session when usage limit resets
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
Make sluggification visible, customizable, and fail-safe
Default sluggification is simplistic, relying on a title field and performing no inference whatsoever. **With no field named "title", entries currently fail to save.** The ideal fix is to simply make slugs editable in the editor UI. Considerations: * Slug editing can be switched off through config * If slug editing is switched off, each collection config must be validated on CMS load to ensure a slug can be derived * Prepopulate with the same best guess or configured slug template result that we currently use * Only valid characters may be entered in the slug field * Slugs and filenames are not always the same, so it should be possible to provide them separately somehow (see [comment](https://github.com/netlify/netlify-cms/issues/445#issuecomment-377425752) below for example)
Comments (0)
No comments yet. Start the discussion.