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

Packages (.ezpkg) and the package creator

The other way to distribute: .ezpkg packages made with the package creator in the administration or ezpm.php - extension exports, content class exports, site styles - and when to use them next to Composer.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/extension-development/part-7-releasing/packages-ezpkg.md

On this page

Packages (.ezpkg) and the package creator

Part 7, chapter 10. Before Composer, extensions and content were exchanged as packages: .ezpkg archives that the administration can create, upload and install. Exponential 6 still supports them, and they remain the right tool for some jobs. This chapter explains when to use them and how to make one. The full guide is Packages: what they carry, where they live, and how to handle them safely.

Composer or a package?

You distributeUse
An extension (PHP, templates, settings)Composer (Composer and Packagist)
Content classes a theme or an extension expectspackages, shipped inside the extension (as sevenx_themes_simple does in packages/)
Example or demo contentpackages
An extension for sites that are not installed with Composeran extension export package, in addition to Composer

Making a package in the administration

Create new package on the packages page opens /package/create, with one wizard per kind your role may use: content object export, content class export, extension export and site style. The wizard asks for the parts, then name, summary, version, license and maintainer, and the format the package is kept in (classic XML or JSON), and writes the package into the local repository. Nothing on the site changes. The policy package/create controls who may use it.

Then download it from the package's page (policy package/export): that is the .ezpkg file.

Making and handling packages from the shell

php ezpm.php list                                   # the packages of the repositories
php ezpm.php export mytheme_classes -d var/tmp      # write an .ezpkg (only reads the package)
php ezpm.php import var/tmp/mytheme_classes.ezpkg   # the same archive checks as the upload page
php ezpm.php help                                   # every command

(Add --allow-root-user when you run them as root.) ezpm.php is at the root of the installation.

Packages inside your extension

For a theme or an extension whose templates expect content classes:

  1. Create the classes on a development site.
  2. Export them with the content class export wizard; set the package's version and license to match the extension.
  3. Put the .ezpkg files into the extension's packages/ folder.
  4. In the README, tell users how to import and install them (the upload page of the packages list, or ezpm.php import).

Version the package files with the extension: a changed class means a new package version in the next release.

Safety

The kernel checks every uploaded or imported archive: paths that point outside the package, links and devices are refused (the guide, sections 6 and 12). Build packages with the wizard or ezpm.php export, never by hand-packing a directory with links in it. Do not put secrets or personal data into packages: example content must be made up.

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