Sign up to our newsletter to receive updates on Winter CMS releases,
new features in the works, and much more.
We'll never spam or give this address away.
Plugins can have localization files in the lang subdirectory of the plugin directory. Plugins' localization files are registered automatically. The localization strings are supported automatically in the back-end user interface menus, form labels, etc. - if you provide the localization key instead of a real string, the system will try to load it from the localization file. In other cases you need to load the localization string with the API.
Note: For translating front-end content, there are plugins that can be used for this purpose.
Below is an example of the plugin's lang directory:
plugins/ acme/ todo/ <=== Plugin directory lang/ <=== Localization directory en/ <=== Language directory lang.php <=== Localization file fr/ lang.php
The lang.php file should define and return an array of any depth, for example:
<?php return [ 'app' => [ 'name' => 'Winter CMS', 'tagline' => 'Getting back to basics' ] ];
The validation.php file has a similar structure to the lang.php and is used to specify your custom validation messages in a language file, for example:
<?php return [ 'required' => 'We need to know your xxx!', 'email.required' => 'We need to know your e-mail address!', ];
The localization strings can be loaded with the
Lang class. The parameter it accepts is the localization key string that consists of the plugin name, the localization file name and the path to the localization string inside the array returned from the file. The next example loads the app.name string from the plugins/acme/blog/lang/en/lang.php file (the language is set with the
locale parameter in the
config/app.php configuration file):
System users can override plugin localization strings without altering the plugins' files. This is done by adding localization files to the lang directory. For example, to override the lang.php file of the acme/blog plugin you should create the file in the following location:
lang/ <=== App localization directory en/ <=== Language directory acme/ <=== Plugin / Module directory blog/ <===^ lang.php <=== Localization override file
The file could contain only strings you want to override, there is no need to replace the entire file. Example:
<?php return [ 'app' => [ 'name' => 'Winter CMS!' ] ];
Published April 12, 2021
We regret to inform you that October CMS as you have known it for the past 7 years is no more. The founders have decided to make it a paid proprietary product; unfortunately abandoning the open source community in the process as "source partially available" is not open source. The core maintainers of the project have forked, and will continue development as Winter CMS....