Package types
Every package has a type, named in its package.xml as <type value="..."/>. The types are listed in package.ini [PackageSettings] TypeList[]; the Type limitation of the package policies names them.
| Type | Holds | Created with | Installed |
|---|---|---|---|
| contentclass (Content class) | Definitions of content classes | Content class export | Yes |
| contentobject (Content object) | Content objects, optionally with their classes and templates | Content object export | Yes |
| extension (Extension) | The files of extensions | Extension export | Yes |
| sitestyle (Site style) | Stylesheets and images of a design theme | Site style | No, imported only |
| site (Site) | The settings and dependencies of a whole site | By hand | No, used by the setup wizard |
Content class and content object packages
A content class package carries class definitions to another installation. A content object package carries content: the nodes and subtrees chosen in the wizard, and optionally their classes and the templates that display them. Both are serialized by the datatypes themselves.
Extension packages
They carry the files of an extension to an installation that does not get it through Composer. The extensions of a standard installation are installed by Composer, and no site package copies an extension's files over the Composer copy any more (see Site packages no longer install extension packages).
Site style packages
A site style package holds a thumbnail, two stylesheets (the colors and backgrounds of the page layout, and the styles of the class templates) and their images. It is imported, never installed or uninstalled.
In the 3.x and 4.x releases a site style chosen under Design > Look and feel replaced these stylesheets of the site. Today Look and feel opens the edit form of the site's look object (menu.ini Links[look_and_feel], content/edit/54 as shipped), as the site packages that have one define it.
Site packages
A site package (such as sevenx_site, ezwebin_site, ezdemo_site, plain_site) contains no objects. It holds settings and the list of packages it requires: classes, content, design. The setup wizard lists the site packages of the remote repository and of the local repositories, downloads the one chosen with every package it requires, imports them and installs the ones that can be installed. Removing a site package from a repository later does not change the installed site. There is no wizard to create site packages; they are written by hand.
Example: ezdemo_site requires ezdemo_extension, ezflow_extension, ezdemo_classes and ezdemo_democontent.
More
Contributors
- Svitlana Shatokhina
- Geir Arne Waaler
- Kristof Coomans Commenter
- Graham Brookins Updated Maintainer
Comments (1 historical)
Written by readers of the earlier documentation sites, kept as they were.
Matching of content class and content class attributes in content object packages
Kristof Coomans ·
For who's wondering how the matching work of content class and content class attributes works when content object packages are imported:
- package system first tries to fetch content class with remote id
- if previous step fails, it tries to fetch content class with the identifier
- content class attributes are matched by identifier only (although the package format does contain their exported remote id)