๐งฉ Architecture & Core Logic
- Super Powers
- Joomla Powers
- Compile Native Components, Plugins & Modules
- Multi-Version Support
- Conditional Logic Injection
- Reusable Admin Views
- Dynamic GET Builder
- Round-Trip Code Integration
- Custom Admin Views
- Site Views
- Dynamic Dashboards
- Model Linking Between Views
- Shared Field Reuse Across Views
- Drag & Drop Field Mapping
- Dynamic Field Visibility
- Independent Packaging
๐ Joomla CMS Integration
๐งฑ Custom Code System (Powerful Dual Feature)
๐ Field Type System
๐ Snippets, Templates, Layouts, Libraries
- Snippets Reusable Html Blocks
- Layouts Reusable Php Render Templates
- Templates Page Level Views Linked To Custom Admin Site Views
- Libraries JS CSS Assets Linked To UI
- CDN Local Toggle For Library Delivery
- Media Folder Injection With Override Support
- Repository Push Pull Reset Workflow
- Init Snippets Layouts Templates Via Gui
๐ฆ Packages
๐งฉ Architecture & Core Logic
๐ File & Code Management
๐ง Code Reuse & Blueprints
๐ Joomla CMS Integration
๐จ Visual GUI & UX
๐ Internationalization
๐ฆ Packaging & Distribution
โ๏ธ Compiler Engine Features
๐งฑ Custom Code System
๐ Field Type System
๐ Dynamic GET (Visual SQL Engine)
๐ Snippets, Templates, Layouts, Libraries
๐ Documentation & Metadata
๐ Analytics & Insights
๐งฉ Architecture & Core Logic
- Super Powers
- Joomla Powers
- Compile Native Components, Plugins & Modules
- Multi-Version Support
- Conditional Logic Injection
- Reusable Admin Views
- Dynamic GET Builder
- Round-Trip Code Integration
- Custom Admin Views
- Site Views
- Dynamic Dashboards
- Model Linking Between Views
- Shared Field Reuse Across Views
- Drag & Drop Field Mapping
- Dynamic Field Visibility
- Independent Packaging
๐ Joomla CMS Integration
- Token Integration
- ACL Per View, Field, Item
- Field-Based Joomla Config Generation
- Support For Joomla Categories/Tags/Custom Fields
- CLI-Ready Components
- Joomla Update Server Integration
- Version-Aware Language String Compilation
- Remote Publishing to Custom Repo Update Streams
๐ Field Type System
- Field Types Define Templates And Data Types
- Gui Defined Rules Required Unique Nullable
- Save Get Hooks Per Field
- Database Schema Auto Generated From Field Settings
- Per Display Field Rendering Config List Edit
- Create Dynamic Models With Modals Selectors
- Conditional Js And Css Per Field
๐ Snippets, Templates, Layouts, Libraries
- Snippets Reusable Html Blocks
- Layouts Reusable Php Render Templates
- Templates Page Level Views Linked To Custom Admin Site Views
- Libraries JS CSS Assets Linked To UI
- CDN Local Toggle For Library Delivery
- Media Folder Injection With Override Support
- Repository Push Pull Reset Workflow
- Init Snippets Layouts Templates Via Gui
Per-Joomla-Version Language Key Mapping
future-proof multilingual support and precise control over your component's UI tone across the Joomla ecosystem
What Is Per-Version Language Key Mapping?
Some Joomla language keys and system responses change between major versions. With per-Joomla-version language mapping, you can define alternative language constants based on the target Joomla version being compiled.
JCB automatically detects the target version during the build process and inserts the correct language strings for:
- Admin & Site interfaces
- Field labels and tooltips
- Error and success messages
- Form instructions
- Menu text and more
Example
Letโs say you have a label:
COM_EXAMPLE_SAVE_BUTTON = "Save"
But in Joomla 5, the UI recommends using โApplyโ instead. You can configure:
- Joomla 3/4:
COM_EXAMPLE_SAVE_BUTTON = "Save"
- Joomla 5+:
COM_EXAMPLE_SAVE_BUTTON = "Apply"
JCB will automatically inject the correct value into the .ini language files for the target version.
Use Cases
- Multi-version component distribution (J3 to J5+)
- Avoid deprecated language keys
- Tailor UI to new Joomla terminology
- Support different user expectations across Joomla versions
Benefits
- ๐งฉ Version-Aware Language Packaging
Each build gets a tailored set of language strings, without bloating a single file with all variants. - ๐ฏ Precision Localization
Ensure that the UI language reflects best practices and terminology for the current Joomla version. - ๐ Seamless Upgrade Paths
Reduce migration effort and improve compatibility with future Joomla releases. - ๐ ๏ธ Full Control via GUI
Manage version-specific overrides directly in JCBโs language configuration panels.
How to Configure
- In JCB, navigate to the Language Strings area.
- Define your language strings as usual โ no manual version-mapping is required.
- When compiling a component, JCB detects the Joomla version and automatically adjusts the language strings accordingly.
- Simply save your strings and compile โ JCB handles version-specific output during the build process.
Conclusion
Per-Joomla-version language key mapping gives you future-proof multilingual support and precise control over your component's UI tone across the Joomla ecosystem. Itโs ideal for developers maintaining extensions across versions or preparing for JED compliance.
Summary
Joomla Component Builder (JCB) supports dynamic language key mapping across multiple Joomla versions. This ensures that your component uses the correct, version-specific language stringsโallowing you to maintain full compatibility with Joomla 3, 4, 5, and beyond from a single blueprint.