๐งฉ 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
Component Update URLs via GUI Settings
the professional way to deliver long-term value with minimal friction
What It Does
The Component Update URL setting in JCB inserts Joomla-compliant update server information into your component's manifest during compilation. This enables Joomla to:
- Check for newer versions of your component
- Download and install updates automatically
- Trust the source using your defined metadata
Where It Lives
In JCB, you'll find the "Update Server URL" field within the Component Settings panel. Here you can:
- Enter one or more update URLs
- Choose the version compatibility (e.g. only for J4+, J5+, etc.)
- Define the release type (e.g. stable, testing, dev)
- Set the update server as default or optional
How It Works
During compile:
- JCB injects
<updateservers>
into your component's XML manifest - This includes all the URLs, types, and attributes you defined in the GUI
- Joomla reads this when installing or updating the component
- Joomla polls that URL on the update schedule (daily or manually)
When a new version is found:
- Joomla displays the update in the Extension Manager โ Update tab
- Clicking "Update" downloads and installs the latest release automatically
Use Cases
- ๐ Remote Package Delivery
Host your updates on a private Git repo, CDN, or your own update server. - ๐งช Multiple Channels
Provide different update paths (e.g. Stable, Beta, Nightly) with version tags and filtering. - ๐ Controlled Rollouts
Deliver updates only to customers or sites with access to specific update servers. - ๐๏ธ Dynamic Integration
Combine this feature with JCBโs Git sync and packaging system to automate end-to-end delivery.
Benefits
- โ No need to manually edit manifest XML
- โ Fine-grained version and release control
- โ GUI-driven, with safe compile-time validation
- โ Seamless Joomla integration using core update logic
- โ Works with both J4 and J5 extensions
Best Practices
- Use separate update URLs for different environments (e.g. dev, prod)
- Host an XML update manifest that points to the actual ZIP downloads
- Include a changelog and hash in the update metadata for trust
- Test the update server response using Joomlaโs built-in "Find Updates"
Example XML Added to Manifest
<updateservers> <server type="extension" name="JCB Update Server">https://yourdomain.com/updates/extension.xml</server> </updateservers>
Conclusion
By managing your update URLs directly from the JCB interface, you make it easy to distribute, track, and manage updates for your Joomla components โ whether open-source, internal, or commercial. Itโs the professional way to deliver long-term value with minimal friction.
Summary
Easily manage Joomla update server URLs for your components directly from the JCB GUI. This feature allows you to define where Joomla should look for future updates of the compiled extension โ without having to write XML or edit update server files manually.