You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I generate the title of a collection entry automatically with a configuration set in the collection settings…
…and use this title afterwards for my slug slug in the blueprint
…the slug converts german Umlaute not as usual. a ö ü becomes a o u instead of ae ou ue.
But if I dispense with automatic titles and use a single title field in my blueprint, the characters ä ö ü in the slug converts to ae oe ue, which is intentional and good.
You can see the difference in the two screenshots:
(In my usecase I would hide the slug field in the blueprint, but I would like to use the readable slug in the entry filename instead of the ID.)
How to reproduce
Create a collection and a blueprint with some text fields (like pre- and surname)
Use the pre- and surname fields in your title format in the collection settings
Add a new entry with Umlaute Ä Ö Ü
Compare the spelling of the generated slug with the slug of an entry from an other collection, where you enter the same name, but directly in the title field of the entry.
Logs
No response
Environment
Application Name: StatamicLaravel Version: 9.38.0PHP Version: 8.1.11Composer Version: 2.4.3Environment: localDebug Mode: ENABLEDURL: test.testMaintenance Mode: OFFCacheConfig: NOT CACHEDEvents: NOT CACHEDRoutes: NOT CACHEDViews: CACHEDDriversBroadcasting: logCache: statamicDatabase: mysqlLogs: stack / singleMail: smtpQueue: syncSession: fileStatamicAddons: 0Antlers: regexVersion: 3.3.50 Solo
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
regex (default)
Additional details
No response
The text was updated successfully, but these errors were encountered:
Bug description
If I generate the title of a collection entry automatically with a configuration set in the collection settings…
…and use this title afterwards for my slug slug in the blueprint

…the slug converts german Umlaute not as usual. a ö ü becomes a o u instead of ae ou ue.
But if I dispense with automatic titles and use a single title field in my blueprint, the characters ä ö ü in the slug converts to ae oe ue, which is intentional and good.
You can see the difference in the two screenshots:
(In my usecase I would hide the slug field in the blueprint, but I would like to use the readable slug in the entry filename instead of the ID.)
How to reproduce
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
regex (default)
Additional details
No response
The text was updated successfully, but these errors were encountered: