Languages

Interface text

Catalogs live in src/Locale/en.php and src/Locale/cs.php. Templates use {t 'key'}. The URL prefix selects Czech at /cs/; the default English URL has no prefix. Add a locale in the application settings and provide its catalog before linking to it.

Database content

Default-language fields remain in cms_sites, cms_menu, and cms_articles. Translation tables contain the other locale. Missing translated values fall back to the default field. Article translations also carry their own content_format, so English Markdown can coexist with Czech legacy HTML during a gradual migration.

After content changes, use the application's normal cache invalidation path. For public production URLs, set i18n.baseUrl to a trusted HTTPS origin so alternate-language links do not depend on an untrusted Host header.

Addresses, links and statistics

With urlPrefix on, a language has its own address prefix: /cs/blog/ is the Czech version of /blog/, and the default language has no prefix. The layout gets the variables lang, locale, alternates (the address of the current page in every language, for the language switcher) and hreflangs (the same as absolute addresses, with x-default). Every page also has one canonical link with the absolute address of the page in its own language. The sitemap lists each language of a page that has a translation, with links to the others. See Search engines.

Pages, menu entries and articles are translated independently, and a page without a translation shows the default language. The API lists the languages that each page, menu entry and article has (translation_locales) and takes translations per language. The assistant of the MCP server uses that to warn when a page, a menu entry or an article lacks a translation for a language of the site.

The statistics record the views of a page per language, and the totals are the sum of all languages (see Statistics).