Glossary for extension developers
Part 8, reference 34, the last page of the book. The terms of Exponential development, as this book uses them.
| Term | Meaning | See |
|---|---|---|
| access word | the answer of hasAccessTo(): yes, no or limited | eZUser and access checks |
| admin4 | the current administration design, with shared components and design tokens | admin4 components and tokens |
| append file | an extension's or siteaccess's <name>.ini.append.php that adds to a kernel INI file | INI files an extension author meets |
| attribute | one field of a content object, of a datatype defined by its class attribute | eZContentObject |
| autoload array | the generated map from class names to files (var/autoload/, autoload/) | Autoloads and class naming |
| cache block | a part of a template whose output is cached (cache-block) | Cache tags, cache blocks and clearing caches |
| class (content class) | the type of a content object: its identifier and attributes | eZContentClass and its attributes |
| cluster file handler | the layer through which files under var/ are read and written, so several servers share them | eZFile, eZDir and cluster file handlers |
| Content Security Policy (CSP) | a header that tells the browser which scripts and styles it may run | CSP: moving inline scripts into files |
| context menu | the right-click menu of the content tree, extended through admininterface.ini | Context menus and admin integration |
| cronjob part | a group of cronjob scripts run together | Cronjob parts |
| datatype | the code behind a kind of attribute: editing, storage, display | The eZDataType API |
| design | a named set of templates and files, searched in the design chain | Themes are extensions |
| design chain | the ordered list of designs (and their extension folders) a siteaccess searches | The design chain |
| design extension | an extension that contributes design folders (DesignExtensions[]) | The anatomy of a design extension |
| design token | a named value (--a4-ink) used instead of a fixed color or size | Dark mode and design tokens in themes |
| expui (Exponential UI) | the administration's JavaScript library, Exp | The expui JavaScript API |
| extension | a folder under extension/ that adds to or changes the kernel without editing it | What an extension is |
| extension point | a registered way for an extension to plug in | Extension points at a glance |
| fetch function | a read operation of a module, called from templates with fetch() | Built-in fetch functions by module |
| fork | a copy of a repository that you maintain | When to fork, and when not to |
| form token | the per-session secret every POST of a signed-in user must carry | ezformtoken and CSRF protection |
| handler | a class named by a setting that provides a service (mail transport, image handler) | Handlers named by settings |
| kernel | the core of Exponential: kernel/, lib/, settings/, the shipped designs | |
| kernel override | an extension's replacement of a kernel class: the last resort | Kernel overrides: the last resort |
| module, view | a group of pages under one URL prefix, and one page of it | eZModule and module results |
| node | a location of a content object in the content tree | eZContentObjectTreeNode |
| object (content object) | one piece of content, with versions and translations | eZContentObject |
| override (template override) | a rule that picks another template for certain content | Template overrides |
| packer | ezjscore's bundling of stylesheets and scripts | Theme assets, the packer and CSP |
package (.ezpkg) | an archive of classes, content or an extension for the package system | Packages (.ezpkg) and the package creator |
| pagelayout | the template that frames every page | View results, the path and the pagelayout |
| persistent object | a class mapped to a table row (eZPersistentObject) | eZPersistentObject |
| policy, role, limitation | a permission (module and function), a set of them given to users, and its restriction | Policy functions and access |
| RAD tools | the wizards of Setup > RAD that write extension code | The RAD tools tour |
| remote ID | a stable, installation-independent ID of an object or node | eZContentObject |
| server function | a PHP method callable through /ezjscore/call/ | ezjscore server functions reference |
| siteaccess | one entry point of an installation, with its own settings and designs | Siteaccess settings |
| tag (Git) | a name for one commit, used as a release version; permanent once pushed | Tags and releases are permanent |
| template operator, template function | {$x|operator} and {function}...{/function} | Built-in template operators |
| trigger | the link between an operation (publish) and a workflow | Triggers and workflows for developers |
| Velocity | the application server of Exponential, required by composer.json since 6.0.15 | |
| view mode | how content is shown: full, line, embed and your own | View modes for builders |
| view parameter | a (name)/value pair in a URL | View parameters |
| workflow, workflow event | a list of steps run by a trigger, and one step | The eZWorkflowType API |
Demo mode - EXP_DEMO_MODE=1 in the environment: administrator passwords cannot be changed or reset (the expDemoMode API, the store guard in eZUser::store()), and the installers accept the published demo password. Demo mode for developers.
Related pages
- Previous: expservices: remote services for extensions
- Next: Book index: every topic from A to Z
- Extension development: the book
- 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.