Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Default blueprint name is wrongly singularized for non-English collection titles

Open
  • Is something wrong?
#15,557 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
laravel, php
Domain
backend, internationalization

Research direction

Start by locating where Statamic generates a default blueprint and applies Str::singular() to the collection title or handle. Reproduce the issue with the German collection title “Aktuelles” and inspect the generated blueprint name and handle. Done means the default blueprint keeps an appropriate German name and handle, and entries continue to reference that blueprint correctly.

Written by the indexing model from the issue text.

Description

i18n
Bug description

When a collection has no saved blueprint yet, Statamic generates a default blueprint and names it by singularizing the collection's title and handle with Str::singular(). That only applies English rules, so non-English titles can end up with a grammatically wrong blueprint name.

Example (German): a collection titled "Aktuelles" gets a blueprint titled "Aktuelle" with the handle aktuelle. "Aktuelles" is not a plural, and "Aktuelle" is not a correct word in this context. Same happens with "Verzeichnis" → "Verzeichni".

Image
How to reproduce
  1. Set the Control Panel language to German.
  2. Create a collection titled "Aktuelles".
  3. Open the collection's blueprints.

The blueprint is titled "Aktuelle" (handle aktuelle). Entries created in this collection are saved with blueprint: aktuelle.

Expected: the blueprint is titled "Aktuelles" (and ideally has the handle aktuelles).

Logs
Environment
Environment
Laravel Version: 13.34.0
PHP Version: 8.4.23
Composer Version: 2.10.1
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: de_CH

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: background
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 1
License Key: Set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.34.1 PRO

Statamic Addons
statamic/seo-pro: 7.15.0
Installation

Fresh statamic/statamic site via CLI

Additional details

No response

Dominant language
PHP
Stars
4.9k
Forks
647
Avg merge
1d 8h
Merged PRs (30d)
100

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from statamic/cms

All issues in statamic/cms

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.