Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Extension bundles

How to ship several Exponential extensions as one bundle - a Composer meta package or a documented set, dependencies in extension.xml, loading order, version and license fields that agree, the secret check for exported…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/bundlers/extension-bundles.md

On this page

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

  1. Forms of an extension bundle
  2. Dependencies
  3. Loading order
  4. Metadata that agrees
  5. Packaging an extension as .ezpkg
  6. Testing and maintaining

Forms of an extension bundle

FormHowGood for
A Composer meta packagea package whose composer.json only requires your extensions at matching versionssites installed with Composer, which is every current installation
A documented seta README listing each package and versionsmall sets
A site package that activates thema site package whose settings list the extensionsnew 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.php and extension.xml state the same Version, license, copyright and info URL; "//autogentag// and dev-master are not versions" (Extension metadata);
  • composer.json names the same license as an SPDX identifier;
  • an extension with its own share/filelist.md5 refreshes 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.

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.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x