Packages in the administration
This section is for administrators who look after the packages of an installed site in the browser, and for developers and hosts who want to know what those pages do before they let editors near them. It answers: where the package pages are, what each one changes, and which policy opens it.
Site packages themselves are installed by the setup wizard, the kickstarter or exp:install, not from these pages
(How the setup wizard uses packages). What you see here afterwards
is what those installers imported, plus anything you upload, fetch or create.
Contents
The pages
| Page | Where | Explained on |
|---|---|---|
| Package list | Setup > Packages, /package/list[/<repository>] | The package list and package page |
| A package's page | /package/view/full/<name>[/<repository>] | same page |
| Import (upload) | Import new package, /package/upload | Importing a package |
| Install, uninstall | /package/install/<name>, /package/uninstall/<name> | Installing and uninstalling |
| Create | Create new package, /package/create | The package wizard |
| Package servers | Setup > Updates and packages > Package servers, /update/servers | Package servers in ezupdate |
| A server's packages, fetch | /update/packages/<server> | Fetching packages with ezupdate |
| Who may do what | roles and policies | Permissions for packages |
The reference for every detail of the kernel's pages is Packages; this section is the task-oriented way in.
Two modules
| Module | Comes with | Does |
|---|---|---|
package (kernel/package/module.php) | the kernel | lists, shows, compares, downloads, uploads, installs, uninstalls, creates and removes packages in the local repositories below var/storage/packages/ |
update (extension/ezupdate/modules/update/module.php) | the ezupdate extension (se7enxweb/ezupdate in composer.json) | Composer updates, and the .ezpkg package servers: lists a server's packages and fetches one into the local repository |
ezupdate fetches; the kernel's pages install. A fetched package appears in the package list like an uploaded one.
What can change the site
| Action | Changes |
|---|---|
| Viewing, comparing, downloading, validating | nothing |
| Importing (upload) or fetching | adds a package directory below var/storage/packages/; the site's content and settings stay as they are |
| Installing | runs the package's install items: classes, content, files, settings, extensions, as the package says |
| Uninstalling | runs the uninstall items: "removes what the items below created on this site, content included. It cannot be undone." |
| Removing | deletes the package directory; what it installed stays |
| Adding a package server | writes settings/override/ezupdate.ini.append.php |
Warning
Install and uninstall on a copy of the site first. Both change content and settings, and the package pages offer no undo.
When the configuration is managed by the deployment
With site.ini [ConfigurationSettings] ManagedByDeployment=enabled, "settings, templates and code come from the
deployment only" (kernel/classes/expmanagedconfiguration.php). Then package/upload, package/install,
package/uninstall, package/create and package/export are locked in a web request like a switched-off module, the
remove actions of the list are refused, and settings files are not written from the browser. The list, a package's
page and Compare stay open. The command line (ezpm.php) keeps working.
Related pages
- Site packages: start here
- Packages
- ezupdate: updates and packages in the admin
- About and package pages
- Making your own site package
- Contribute your site package
- 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.