If you are a third party developer and create software for Elxis CMS (components, modules, bots, bridges, tools), or a template designer or even a translator we advice you to follow Elxis naming standards in your final package. In general you should create a ready to install zip package which name should follow this format:

type_name_version.zip

Where type is the type of the extension, name your extension's name and version your extension's version

Extension type

• tpl, for front-end and back-end templates and login screens
• com, for components
• mod, for modules
• bot, for bots
• lng, for language packages
• tool, for elxis tools
• bri, for elxis bridges

Extension name

As the extension name you should use the name used in XML parameters file. For example if you have created a component named com_mytest then add "mytest" as your extension name in the final zip package.

Notice 1: For templates the name should be followed by the template type. Valid template types are: frontend, backend and login. You can omit the template type if it is for front-end.
Notice 2: For language packages the name should be followed by the area that the package provides multi-linguism. Valid language areas are: frontend, backend, help and install.

Extension version

The version of your extension.
Notice: For language packages the version should be the exact elxis version the package provides multi-linguism for.

Examples

com_mytest_1.0.zip
mod_mysupermodule_1.3.1.zip
bot_myelxisbot_1.0.zip
tpl_redhome_1.0.zip
tpl_reddragon_backend_1.0.zip
tpl_redalert_login_1.0.zip
lng_english_frontend_2008.0.zip
lng_greek_backend_2008.0.zip
lng_german_help_2008.0.zip
lng_italian_install_2008.0.zip
tool_spacetravel_1.0.zip
bri_elxis2008_smf14_1.0.zip