Extension bundles
This page is for developers and companies who ship a set of extensions that belong together: a shop suite, an intranet kit, an SEO pack. The single-extension checklist is Publishing an extension; this page covers the set.
Contents
- Forms of an extension bundle
- Dependencies
- Loading order
- Metadata that agrees
- Packaging an extension as .ezpkg
- Testing and maintaining
Forms of an extension bundle
| Form | How | Good for |
|---|---|---|
| A Composer meta package | a package whose composer.json only requires your extensions at matching versions | sites installed with Composer, which is every current installation |
| A documented set | a README listing each package and version | small sets |
| A site package that activates them | a site package whose settings list the extensions | new sites built around the set (Site packages in a bundle) |
Each extension remains its own Composer package with its own repository and tags.
Dependencies
extension.xml declares dependencies between extensions:
<dependencies>
<requires>
<extension name="ezjscore" />
</requires>
<extends>
<extension name="ezwt" />
</extends>
</dependencies>"<requires> names extensions that must be active; <extends> names extensions this one builds on"
(Extension metadata). Mirror the same dependencies in each
composer.json so Composer installs them.
Loading order
The order of ActiveExtensions decides whose settings and templates win. Document the order your bundle needs and
test it; Setup > Extensions shows it (Extension list,
Loading order and safe saving).
Metadata that agrees
For every extension in the set:
ezinfo.phpandextension.xmlstate the sameVersion, license, copyright and info URL; "//autogentag//anddev-masterare not versions" (Extension metadata);composer.jsonnames the same license as an SPDX identifier;- an extension with its own
share/filelist.md5refreshes it in the same release, because the admin's file consistency check lists every stale line as a modified file (Integrity checks).
Packaging an extension as .ezpkg
Setup > Extensions and ezpm.php add can pack an extension as a package, but exporting is off by default and needs
package.ini [ExtensionExportSettings] AllowedExtensions[] and the policy package/export_extension. "An extension
that holds a secret value or key material is not packed" (The secret check).
For a bundle, Composer packages from your repositories are the primary form; use .ezpkg where recipients install
through the package system.
Testing and maintaining
- To do: Install the whole set on a clean installation of each Exponential version you support, on each database you claim.
- To do: Activate in the documented order; run
php bin/php/console exp:checkclasses, which "loads every declared class and reports those PHP refuses to load" (10.7). - To do: Test against each new Exponential release (Testing releases).
- To do: Release the set together, with one changelog naming each extension's version.
Related pages
- Publishing an extension as a partner
- Extension and theme partners
- Publishing extensions from a bundle
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.