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

Glossary

Every term the documentation uses, in one line, with a link to the page that teaches it. Terms are in alphabetical order. A term in bold inside a definition has its own entry. For a first walk through the product, use…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/glossary.md

On this page

Glossary

Every term the documentation uses, in one line, with a link to the page that teaches it. Terms are in alphabetical order. A term in bold inside a definition has its own entry. For a first walk through the product, use the guides; for the story behind a term, use the history.

In short

  • One line per term; follow the link for the how-to, the settings and the examples.
  • Names that start with exp or sevenx are extensions or classes from 7x (exp marks work 7x assigns to the Exponential project and the Exponential Foundation); names that start with ez are older extensions and kernel identifiers that keep their names. Naming prefixes: sevenx and exp.
  • Commands are shown as you type them in the installation root: ./console exp:<name> is the same program as php bin/php/<name>.php.

Contents

A · B · C · D · E · F · G · H · I · J · K · L · M · N · O · P · Q · R · S · T · U · V · W · X · Y · Z

A

  • admin, admin2, admin3, admin4, classic: the administration designs. admin3 works on phones and wide screens; admin4 is a complete design with a light and a dark mode; classic is the grey interface without YUI. See admin3, admin4, admin4l (admin4 built from layouts), admin classic theme.
  • AdminAid: an extension with a debugging helper for administrators. AdminAid.
  • adminneo: a database manager (a fork of Adminer), embedded in the admin by the DSE extension. AdminNeo.
  • Apache: the web server that can run the installation together with PHP-FPM. Deploying.
  • attribute: one field of a content class, typed by a datatype. Content model.
  • audit channel: one of the five hash-chained streams of the audit trail (content, access, system, commerce, read). Audit event model.
  • audit source: a class an extension registers in audit.ini [AuditSourceSettings] Sources[] to show its own channel in the audit console (panel, links, charts, CSV columns). Audit guide.
  • audit trail: a tamper-evident log of security-relevant events (sign-ins, content changes, settings writes, cache clears). Audit trail, event model.
  • autoload: the generated class maps (var/autoload) that tell PHP where each class lives; regenerate with php bin/php/ezpgenerateautoloads.php. Operating a site.

B

  • background run (migration): a migration run, resume or rollback started in Setup > Migrations, which runs as a console process of its own as the signed-in user and goes on when the page is closed; its files are in var/<site>/migration/jobs/. In the administration.
  • bc note (behaviour change note): a page that says what changed in behaviour and what to check when you upgrade. Behaviour changes, July and August 2026.
  • bcgooglesitemaps: an extension that generates search engine sitemaps as a cronjob. bcgooglesitemaps.
  • bcwebsitestatistics: an extension that sends page views and shop purchases to an analytics service. bcwebsitestatistics.
  • benchmark: measuring an installation: page timings over HTTP, two servers back to back, the kernel in-process, and a comparison with a saved run (exp:benchmark). Benchmark.
  • block (layout): a unit of content placed in a zone of a layout. Exponential Layouts.
  • bridge: see legacy bridge.

C

  • cache: stored results that make pages faster; Exponential has many (content view, template, INI, HTTP, static, SQL query, response). Cache control, Operating a site.
  • cache block: a template tag that caches the markup inside it; the Valkey variant is {valkey-block}. Redis and Valkey caches.
  • cache variant key (UI switch): the short key (language-ger-DE) that keeps caches built with a user's UI switch choice apart: {cache-block}, the content view cache and compiled templates; empty when nothing is chosen, so no cache name changes. UI switch provider API.
  • caption: a safe point of an installation (the database dump, the var/ storage, settings/override, the commits of the code) that exp:upgrade and every migration run take, and that a rollback restores. Rollback and captions, Upgrading with the console.
  • changelog: the release notes of a version, in Added, Updated, Removed and Renamed lines. 6.0.15, extensions.
  • checksum guard: the refusal of a migration recorded as done whose file has changed since; --force --reason=<text> accepts the change. Migrations.
  • chronicle: the month by month story of the history. History.
  • CI (continuous integration): the GitHub Actions workflows: phpunit.yml runs the PHPUnit suites on PHP 8.1 to 8.5, quality.yml checks syntax (also on PHP 8.0), the file manifest, commit messages, code style and PHPStan for every change. Quality checks, Continuous integration.
  • cjw_newsletter: a complete newsletter system. cjw_newsletter.
  • CLA (Contributor Licensing Agreement): the agreement with the Exponential Foundation and 7x that they require, signed once, before a code contribution to the core kernel (se7enxweb/exponential) is merged, however it is submitted (pull request, patch, issue, mail). By signing and submitting, the contributor assigns the copyright in the contribution to the Exponential Foundation and 7x, which become its owners, and gives up control over it: the Exponential Foundation and 7x may use, change, relicense and distribute it in any way, also under other licenses and in commercial products, without asking or paying the contributor, who cannot withdraw it or set conditions on it. Users' own custom extensions are not affected. Copyright assignment (CLA).
  • class: see content class.
  • classic: see admin.
  • cluster (file cluster): file storage in the database or a shared store so several servers see the same files. Operating a site.
  • collected information: answers visitors submit through forms (contact, polls), stored per object and exportable. bccie.
  • Composer: the PHP package manager; the installation's composer.json decides which extensions arrive. Default extension distribution.
  • console: the command ./console, which finds and runs every command of an installation (exp:, bin:, cron:, ext:). Console.
  • consent log: the record of every change of a person's e-mail preferences, with the time, the source, the exact text the person saw and the IP address; anonymised on erasure. E-mail preferences, specification.
  • content checks: Setup > Unreferenced objects and Broken relations: the assets (images, files, media) below a node that nothing uses (to move to the trash), and visible content that refers to deleted, trashed, hidden or unpublished content. The content checks.
  • content class: the definition of a kind of content (for example Article) as a list of attributes. Content model.
  • content finder: Setup > Content finder and a box below the content structure: find the content behind an id, a remote id, a URL alias, a page address or a file path, and act on it within your rights. Content finder.
  • content job: a large remove, copy or move run in the background instead of one web request. Content jobs.
  • content object: one piece of content, an instance of a content class, with versions and translations; it appears in the tree through one or more nodes. Content model.
  • content tree: the hierarchy of nodes shown in the admin; node 1 is its root. Content model.
  • content view cache: the stored result of rendering a node's view; cleared by exp:cache. Cache control.
  • coverage: the generated proof that every change is accounted for in the documentation. Coverage.
  • cron / cronjob part: a scheduled maintenance task (cron:<name>, run by runcronjobs.php). Cronjobs in the console, Operating a site.

D

  • database drivers: MySQL and MariaDB, PostgreSQL, SQLite, MongoDB and Oracle. SQLite, MongoDB, Oracle and SQLite.
  • datatype: the code that stores, validates, edits and shows one kind of attribute (text, image, relation, tags). Datatype and input hardening.
  • deferred (upgrade step): the action a migration run reports for a kernel upgrade step of the stage code, libraries or finish, which it leaves to exp:upgrade. Upgrade step or migration?.
  • design: a set of templates, styles and images; the siteaccess chooses which designs are used. Getting started.
  • design.ini: the settings file that lists designs, stylesheets and scripts. Multi-site INI overrides.
  • detect() (migration): the method of a PHP migration that asks the installation itself whether the change is in place (done, pending, not-needed), instead of the record. PHP migrations.
  • DFS: the database file system flavour of the cluster handler. Operating a site.
  • digest (notification): one e-mail that collects the notification messages of a day, a week or a month instead of one mail per change. Notifications, specification.
  • double opt-in: switching a kind of e-mail on (newsletters, offers) or using a new address only after the link sent to the address is confirmed. E-mail preferences.
  • down() (migration): the method of a PHP migration that undoes its up(), run by exp:migration:rollback <migration-id>; a migration without one is taken back by its run's caption. Writing a reversible down().
  • dry run (console): a run of a changing exp:user command without --apply: it lists what it would change and which checks fail, and changes nothing; --dry-run means the same. User management from the console.
  • dry run (migration): exp:migration:migrate without --apply: every pending migration with what its plan() says it would change, nothing written. Migrations.
  • DSE (sevenx_dse): the Database Source Editor, which embeds adminneo in the admin. sevenx_dse.
  • DXP skeleton: a starter project for the Symfony based platform. Platform DXP skeleton.

E

  • e-mail preferences: the page where each person turns each optional kind of e-mail on or off, sees the history and downloads the data (/mailpreferences/settings). User's guide, administrator's guide, law checklist.
  • engine (web server engine): the program that serves the site: php (built-in server), qbix (Velocity) or frankenphp. Velocity engines.
  • engine.phar: the archive of kernel/, lib/ and autoload/ that Velocity can load. Engine archive.
  • environment (migration): the name of an installation's stage (development, test, staging, production) from site.ini [AdminEnvironment] Level or EXP_ENV; a migration's header line environments: limits it to some. Per-environment migrations.
  • Exp Debug bar: a bar on pages that shows queries, time and template information to administrators. Exp Debug bar.
  • exp (prefix): a code prefix 7x uses strategically, with intent, to build the Exponential brand and to assign ownership of an extension or solution to the Exponential project and the Exponential Foundation (explayouts, expai, expHelpAudience); new kernel code uses it. Naming prefixes: sevenx and exp.
  • exp-user/1: the schema of the JSON output (--format=json) of the exp:user commands; keys are only ever added. exp:user JSON output.
  • exp: the prefix of the console commands that run bin/php/*.php scripts. Console.
  • exp:about: the system card plus the project: what Exponential is, the license, links, how to contribute. The system card.
  • exp:expfetch: the console command that draws the system card: the Exponential "e" next to the facts of the installation, its engine and its machine, with health hints. The system card.
  • exp:info: the system card plus an inventory: extensions and versions, siteaccesses, settings, cronjobs, caches, help coverage. The system card.
  • exp:ini: the command that reads and writes INI settings in every scope. exp:ini.
  • exp:user: the console commands that manage user accounts, groups, roles, sessions and two-step sign-in, as the administration does. User management from the console.
  • exp_enhanced_link: the extension that provides the enhanced link field type. exp_enhanced_link.
  • expcomponents (Exponential Components): Exponential's fork of the Zeta Components, the PHP libraries the kernel is built on (ezcMail, ezcArchive, ezcWebdavServer ...), one Composer package each (se7enxweb/expcomponents-<name>), Apache License 2.0, required by the kernel since 6.0.15; each fork replaces its zetacomponents/<name> package and keeps the class names. expcomponents, upgrade notes, packages, contributing.
  • explayouts: the extensions that bring layouts, blocks, zones and rules to the admin. Exponential Layouts, explayouts_ui, API specification.
  • Exponential Intelligence (expai): the writing assistant of the administration interface; it writes drafts as the editor, with the editor's permissions, and never publishes on its own. expai, README.
  • Exponential Platform: the Symfony based product line (bin/console, exponential:* commands) that can run Exponential 6 through the legacy bridge. Platform package map, command names.
  • expqueue: the job queue extension: priority classes, fair scheduling, retries and a dead letter, run by cron or a systemd worker, Setup > Job queue. expqueue.
  • expservices: the library of remote services built from ezjscore server functions. Remote services, specification.
  • expui (Exponential UI): the JavaScript component layer (exp::*) that replaced YUI in the admin. jQuery 4 and YUI removal.
  • extension: a folder under extension/ that adds settings, classes, modules, templates or designs; activated in ActiveExtensions. Extension list, loading order.
  • extension metadata: version, license and website of an extension, read by the about page. Extension metadata.
  • eZ Components: the original name of the PHP libraries with ezc class names, developed by eZ Systems from 2005 under the New BSD license and needed beside the code by eZ Publish 4.x, the discontinued product Exponential grew from; continued as the Zeta Components and, since 6.0.15, as expcomponents. expcomponents history, migrating from 4.x.
  • ezautosave: automatic saving of the draft in the edit form. ezautosave.
  • ezdemo: the demo website of Exponential. ezdemo.
  • ezflow: the page builder of the classic design (a page datatype with zones and blocks). ezflow.
  • ezformtoken: the kernel extension that protects forms with a token; see form token. Form expired page.
  • ezgmaplocation: a datatype for latitude and longitude. ezgmaplocation.
  • ezie: the image editor inside the edit form. ezie.
  • ezjscore: the JavaScript foundation: packs scripts and styles, loads jQuery, hosts server functions. ezjscore.
  • ezmbpaex: password expiry rules. ezmbpaex.
  • ezmultiupload: upload many files at once into folders and galleries. ezmultiupload.
  • ezodf: import and export of OpenDocument text. ezodf.
  • ezoe: the online rich text editor (TinyMCE 3 and TinyMCE 8). ezoe, TinyMCE 8.
  • ezpaypal: the PayPal payment gateway. ezpaypal.
  • ezpkg: the package archive format (.ezpkg) holding content, classes, templates and files. ezpm, Package compare and import.
  • ezpm (command): the package manager on the command line (ezpm.php). ezpm. Not to be confused with the ezpm extension, which provides private messages: ezpm extension.
  • ezprestapi: the REST API extension that serves REST API v1 and v2 (reads at both, writes at v2) for remote content updates; it replaces the deprecated ezprestapiprovider. ezprestapi, REST API v1 and v2.
  • ezstarrating: a star rating datatype. ezstarrating.
  • eztags: a tag datatype with a managed tag tree. eztags.
  • ezupdate: the package and update checker of an installation. ezupdate.
  • ezwebin: the classic ready-made website. ezwebin.
  • ezwt: the website toolbar editors see on the public site. ezwt.
  • ezxmlexport: scheduled XML export with FTP delivery. ezxmlexport.

F

  • feature page: a how-to page for one user-facing feature, with settings, examples and limits. Features.
  • fetch function: a template function that reads content or system data (fetch('content','list',...)). Content model.
  • file consistency check: Setup > Upgrade check, which compares installed files with the shipped checksums. File consistency check.
  • form token: the hidden value that protects a form against cross-site request forgery. Form expired page.
  • FrankenPHP: a production-ready web engine (Caddy with PHP built in), selectable beside Velocity. FrankenPHP.

G

  • git_manager: web admin tools for the Git side of an installation. git_manager.
  • GraphQL: a query language for APIs in which the client names exactly the fields it wants; the kernel answers it at /api/graphql, with a schema generated from the content classes and the user's policies always applied. The GraphQL API.
  • guide: a tutorial that gets you a working result in minutes. Guides.

H

I

  • INI file: a settings file (site.ini, content.ini, ...) in blocks of Key=Value; read in order, a later file winning: defaults, siteaccess, extensions, override. INI override placements, exp:ini.
  • install type: a named installer of Exponential Platform (exponential-oss, ibexa-oss, exponential-media, exponential-cjw) run by exponential:install <type>. Platform SQLite installer.
  • installation name: the name shown on non-production pages so staging is never taken for production. Installation name.
  • installer / install: ./console exp:install --apply installs a whole site in one command. Install in one command.
  • interface language: the language the administration itself is shown in, chosen per user in the right toolbar (policy uiswitch/language); it sets the locale for that user's requests and never changes the content languages. Interface language, settings.

J

  • job queue: see expqueue; for large content operations see content job.
  • jQuery 4: the JavaScript library of the admin since October 2026; admin4 and admin4l load it only on the pages that request it (23 October 2026). jQuery 4 and YUI removal.

K

L

  • layout (Exponential Layouts): a page structure made of zones that hold blocks, chosen by rules. Exponential Layouts.
  • ledger: the complete record of every commit of every repository. Ledger.
  • legacy bridge: the package that runs Exponential 6 inside the Symfony platform. Legacy bridge, specification.
  • loading order: the order in which active extensions are read; later wins. Extension loading order.
  • location: another word for a node. Content model.
  • log viewer: Setup > Log files (setup/logs) and ./console exp:logs: the log files followed live, searched with their rotations, masked by default, cross-referenced by request and error reference. The log viewer.

M

  • mail category: the kind a mail belongs to (content, newsletter, security, ...), declared with eZMail::setCategory(); essential categories are always sent, optional ones only to people who turned them on. Developer's guide.
  • mail gate: the check in eZMailTransport::send() that every mail passes: it blocks optional mail people did not ask for and adds the footer and the unsubscribe headers. Specification.
  • maintenance mode: takes the site offline with a notice (exp:maintenance on|off|status). Maintenance mode.
  • migrating a site: moving a whole installation to another server, engine or release, or bringing content in from another system; not the same as a migration. Migrations versus migrating a site, Migrating to and from Exponential.
  • migration: a change to an installation (a table, content, a role, a setting) in a file YYYYMMDDHHMMSS_name.php under version control, applied once to every installation of a site in the same order (exp:migration:migrate); not the same as migrating a site. Migrations, the guide, the tutorial.
  • migration source: where a migration comes from: site (migrations/), extension:<name> (an active extension's migrations/), package:<name> (an installed package) or kernel (the upgrade steps of exp:upgrade). Migrations in an extension or a package.
  • migrations repository: the git repository (the site's own, or a separate one) a migration run commits its status file and run log to, tags and pushes. The migrations repository.
  • module: a set of views behind a URL such as content/view; extensions can add or override modules. Extension module override.
  • MongoDB: a supported database. MongoDB.
  • multi-node edit: editing several items in one form. Editing several items at once.
  • multisite package: the site package that exp:install installs by default (sevenx_multisite). Install in one command.

N

  • Nexus: the starter projects of the Symfony based platform. Platform Nexus starter.
  • ngclasslist: a datatype that stores a list of content classes. ngclasslist.
  • ngsymfonytools: lets legacy templates include Twig templates and run Symfony code. ngsymfonytools.
  • node: one place of a content object in the content tree; has an id, a parent, a sort order and a visibility. Content model.
  • notification: an e-mail that tells a user that followed content changed or that a collaboration item needs attention; made from an event by a handler when the notification cronjob runs. Notifications, administrator's guide, specification.
  • nxc_powercontent: an extension that extends how code creates, updates and removes content. nxc_powercontent.

O

P

  • package: a set of content, classes and design that can be exported and installed, in the classic XML or the JSON format, validated on upload and installable in the background or as drafts; also a Composer package. Packages, JSON package format, ezpm, Platform package map.
  • page layout (pagelayout.tpl): the outer template that wraps every page. Templates and design.
  • pending registration: an account whose registration is not finished: it waits for the e-mail address to be confirmed, for an administrator, or for an approval item (exp:user:pending). Approve registrations.
  • phar: see engine.phar.
  • PHP-FPM: the PHP process manager that serves the site behind Apache. Reload the one that serves your site after a PHP change. Deploying.
  • placement (INI): the name of the place a setting's value came from (default, override, extension:<ext>, siteaccess, ...). INI override placements.
  • policy: one permission (module, function, limitation) inside a role. Roles and policies in order.
  • PostgreSQL: a supported database. Install in one command.
  • preload: requesting every published page so no visitor pays for a render (exp:preload, exp:warm, Setup > Preload). Preload view, Preloader.
  • protected account: an account the exp:user commands never disable or remove: the anonymous user, the UserCreatorID user, the administrator account (id 14 or the login admin), the user who acts and the last enabled administrator. Protected accounts.

Q

  • Q settings: the Velocity engine's own settings, JSON under the Q key; from Exponential they are normally set through settings/velocity.ini. Velocity engine settings.
  • Q shell: the drop-down console in the Velocity control panel. Q shell.
  • qbix: the engine name of Velocity inside Exponential's settings and the upstream project it is based on. Velocity engines.
  • query cache (SQL): answers repeated SELECT queries without asking the database until a write makes them stale. SQL query cache.
  • query-string redirect: a redirect of an old address with a query, such as /index.php?id=12, matched on the path and the query (in any order of its parameters) before the URL aliases and wildcards; made by importing a URL map. Importing and exporting URL maps.

R

  • RAD (rapid application development): the extension points that let code add operators, views, commands and datatypes without editing the kernel. RAD tools, extension points, extension surface.
  • reCAPTCHA: a captcha datatype. recaptcha.
  • recipe: a Symfony Flex recipe that configures a package when it is installed. sevenx-recipes.
  • Redis / Valkey: servers that can hold the content view and INI caches. Redis and Valkey caches.
  • registry (rad.ini): a list an extension reads from its own settings or code (event listeners, cronjob parts, audit sources, editor engines), declared in rad.ini so Setup > RAD counts and checks its entries. RAD extension surface.
  • repair page: the page that explains missing libraries and lets an administrator repair them. Repair from the browser, Repair.
  • request rule: a rule in requestrules.ini that allows or refuses a request by module, view and URL. Request rules, securing content/view/full.
  • requires (migration): the header line of a migration that names the migrations, upgrade steps or extension:<name> it must run after. Team workflow with git, the file format.
  • response cache (Velocity): the server's cache of rendered pages. Response cache.
  • role: a named set of policies assigned to users and groups. Roles and policies in order; its users and groups: role assignment paging.
  • rollback (migration): taking migrations back: a run by restoring its pre caption, one migration with its down(), or any caption for experts (exp:migration:rollback). Rollback and captions.
  • RSS: feeds exported and imported by the RSS module; see also syndication. RSS, podcast and feed list.
  • run log (migration): migrations/runs/<run-id>.log, one line per event of a migration run, cleaned of secrets and e-mail addresses, committed to the migrations repository. The audit trail of runs.
  • run (migration run): one call of exp:migration:migrate --apply, with its own run id (YYYYMMDD-HHMMSS-<6 hex>), captions, log, commit and tag; recorded in exp_migration_run. Migrations.
  • run lock: the installation lock var/<site>/upgrade.lock that exp:upgrade and every migration run hold while they write, so only one writes at a time. Migrations.
  • runnable: the class behind a command, cronjob part or module view (Exponential\Runnable\*); can be replaced or listened to through [RunnableSettings]. Commands, cronjob parts and views as classes.

S

  • section: a label on content that selects a design and permissions. Content model.
  • security defaults: the settings that make a default installation safe without extra work (security headers, session cookie, login, served files, caching). Security defaults, datatype and input hardening.
  • seed data: the tables and content a new installation starts with. Installer logs and seed data.
  • setup wizard: the browser installer. Setup wizard.
  • sevenx: 7x's official public PHP code prefix (sevenx_dse, sevenx_valkey_cache). "7x" itself cannot be a prefix because a class or identifier cannot start with a digit; extensions and classes from 7x use sevenx or exp, as 7x needs. 7x is the company that leads Exponential. Naming prefixes: sevenx and exp.
  • shared layout: a layout that exists to be borrowed: a zone of another layout is linked to one of its zones and renders its blocks, so a header or footer is built once. Shared layouts and linked zones.
  • simulation (migration): exp:migration:dry-run --simulate: the pending migrations run for real in a transaction that is rolled back, with --diff showing what changed; PostgreSQL and SQLite only. Testing migrations.
  • site package: the content and design set installed at setup. Clean install defaults.
  • siteaccess: one way of reaching the site (by URL, host or port) with its own settings and design, such as site and admin. Getting started, Multi-site INI overrides.
  • Smaller changes: the section of a chronicle page that lists changes without a story of their own. History.
  • Smarty templates: templates in Smarty 5 (.stpl), rendered by the kernel next to .tpl and .twig. Smarty templates.
  • Solr: the search server controlled by exp:solr. Web server and Solr commands.
  • specification: a reference page for a subsystem: data model, classes, settings, APIs. Specifications.
  • SQLite: the database in one file; the default of exp:install. SQLite, driver specification.
  • state (object state): a label from an object state group, for example the lock state "Not locked", that policies can test; not the same as the status of a version (draft, published). Installer seed data.
  • static cache: pages written to files and served without PHP. Static cache generator, defaults.
  • static publishing: a site built as a folder of plain files and published to a repository, for GitHub Pages or any other static host; set up and run in Setup > Static publishing or with exp:static:*. Each place is a target, each publish a tag static/<target>/<n>. Static publishing, feature.
  • status file (migrations): migrations/status/<environment>.json, the record of one environment's migrations mirrored into git after every run. Pushing tags, the file format.
  • suppression list: the addresses that get no optional e-mail (bounces, complaints, requests), stored only as salted hashes (exp:mail:suppression). Administrator's guide.
  • swark: an extension with many template operators and workflow events. swark.
  • syndication: the extension for export and import feeds. syndication, specification.
  • system card: what exp:expfetch, exp:info and exp:about show, and the name of their code (expSysCard*, syscard.ini): facts from providers, health hints, themes and logos. The system card.

T

U

  • UI switch: the framework behind the Interface box of the administration's right toolbar: a signed-in user's choices for the interface itself (the interface language first), kept in the session per siteaccess and applied early in every request. Interface language, settings.
  • UI switch provider: a class that offers one choice of the UI switch (expUISwitchProviderInterface, usually extending expUISwitchProvider), named in uiswitch.ini [UISwitchSettings] ProviderList[] and guarded by the policy uiswitch/<identifier>. UI switch provider API.
  • URL alias: a readable address mapped to a node; exp:updateniceurls rebuilds them. Content model.
  • URL map: a file (CSV, JSON, .xlsx, .ods, Apache or nginx rules) that lists old addresses and where each one goes; imported into the URL translator, the wildcards and the redirects as one batch that can be undone, and exported again. Importing and exporting URL maps, Migrating URLs.
  • uwebserver: a small C web server shipped with Velocity, used for static files and benchmarks. uwebserver.

V

W

  • warm-up: preparing the Velocity parent process before it forks its workers; also the same word for preload. Velocity worker pool.
  • WebSocket: a long-lived connection between browser and server, supported by Velocity. WebSockets and events.
  • worker: one long-lived PHP process of Velocity that answers many requests. Velocity worker pool.

X

Y

  • YUI: the old JavaScript library, removed in October 2026. YUI removal.

Z

  • Zeta Components: the continuation of the eZ Components under the Apache License 2.0, first in the Apache Software Foundation's incubator (Apache Zeta Components), then as an independent project (zetacomponents/* on Packagist); the kernel's libraries up to 6.0.14, forked as expcomponents since 6.0.15. expcomponents.
  • zygote: a helper process of Velocity that forks new workers so they inherit no visitor connections. Velocity worker pool.

Demo mode - The state of an installation whose processes have the environment variable EXP_DEMO_MODE=1: a public demo. Administrator passwords cannot be changed or reset, the installers accept the published demo password, and the administration shows a banner. Never on a real site. Demo mode.

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