This example Language Module demonstrates the functioning of Language Module extensions within this CMS. Its explaining the use of various folders and provides a skeleton template for creating your own Language modules.

You may download the example module here: Download

• Language modules can override language key values of the Suitefish CMS Administrator module by defining overrides within language.php.
• Multiple language modules can be active simultaneously, with the option to select from the available languages.

1. Method: Login to your suitefish instance and browse our official store on your page. If you find the module you are looking for just download the package. Then navigate to the Language Package Area and enable the downloaded Language.

2. Method: Navigate to the Language Package Area inside the Suitefish instance. Go to the upload section and upload the modules .zip file. Then navigate to the Language Package Area and enable the downloaded Language.

This section provides important information for developers about module development, including essential coding guidelines to be followed prior to submitting or deploying modules.

Please follow these coding guidelines when developing modules:

• The module's Rname identifier must be unique.
• If you plan to publicly release your module, request a unique Rname from the Suitefish staff. Otherwise, prefix your module's Rname with "int" to designate it as an internal, non-public module, avoiding duplication.
• Public image modules should have an Rname starting with "lg".
• Ensure the Rname does not exceed 20 characters.
• Avoid using special characters in the Rname, as they may cause critical errors.

You can override any language keys function by defining your own in this file. See available language keys in ./_site/_administrator/_lang/en.php or through other theme modules. The language library loads only after the Suitefish CMS frontpage initializes, making all documented site module variables and constants available.

Language files in this type of module are used only to display the name and description in the store for multilingual support. Below is an example of an English language file (en.php). The initial lines restrict public access to the file. The translation variables enable the store to present the name and description in multiple languages. The main language file for the administrator interface is language.php.

<?php if(isset($this)) { if(!is_object($this)) { Header("Location: ../"); exit(); } } else { Header("Location: ../"); exit(); } ?>

store_version_name=Template: Theme Module
store_version_description=This example Theme demonstrates the functioning of Theme Module extensions within this CMS. It includes readme files explaining the use of various folders and provides a skeleton template for creating your own Theme modules.

Changelog of changes between this and last version of this module. Store the changelog in simple html format in the $x variable in files fitting the version number at _changes.

$x = "<b>Release 1.10.100</b><br /> - Initial Release";

This file (version.php) contains detailed information about the module, all variables are mandatory and should be set on a module.

If you are a developer you can find examples of modules in the _developers folder at the suitefish-cms github repository if you want to create an own module! For more information about the Suitefish CMS: https://github.com/bugfishtm/suitefish-cms.

🐟 Bugfish