Slugs not working as expected

[lilacpixel]

I'm having a few issues with the slugify functionality of Sveltia--specifically, the top-level slug configuration and hidden widget fields.

First issue:

Given a collection item with a title containing special characters, such as "Keybjört", Sveltia generates a slug of keybjört and creates the file keybjört.md. I'd like to avoid non-ASCII characters in my filenames, so I've added the following top-level configuration to generate ASCII-only slugs:

slug:
  encoding: ascii
  clean_accents: true

When testing this configuration using the local development workflow, there is no change. The slug remains keybjört, and the same filename is output to the source directory.

Second issue:

For whatever reason, the slug template tag doesn't work at all in hidden widget fields.

The following field…

- name: permalink
  widget: hidden
  default: 'portfolio/{{slug}}/index.html'

… produces this output in the item's front matter.

permalink: portfolio//index.html

This, of course, breaks everything, since it would result in every collection item having the same permalink. The same template tag does correctly output a slug when used in the preview_path field.

I've only tested these with the local development workflow, so I'm not sure if the problems might be specific to that particular environment.

Is there something that I've overlooked here? 🤔 It would be great to enable item preview URLs for this client site, but I'm not sure how to do that without either:

• a) switching from my Eleventy-generated permalinks (permalink: portfolio/\{{ title | slugify }}/index.html) to permalinks that use Sveltia's slug generation, or
• b) creating a custom string transformation for passing to preview_path, which would generate the same slugs as Eleventy. (Eleventy uses @sindresorhus/slugify for its slugify filter, which transliterates Unicode characters rather than mapping them to similar ASCII ones.)

Thanks in advance for taking a look!

[kyoshino]

I’ll check the first issue.

The second issue is not a bug. {{slug}} is not available in default because the default value is generated when an entry is created, not when it’s saved. The CMS doesn’t provide a way to embed a permalink in each entry data simply because we think it’s redundant; the filename already contains the slug. That said, we already have similar feature: aliases/redirects support mainly for Hugo. So we could add permalink support for Eleventy if needed.

[kyoshino]

I suspect you added the slug global option after keybjört.md is created. The CMS doesn’t automatically update the slug of existing entries. If you create the same entry after the slug option is added, the filename would be keybjoert.md.

[kyoshino]

You can manually update the slug if needed 🙂

[kyoshino]

v0.259.0 added the permalink_field collection option so a hidden field is no longer required 🙂