- Modules and views Pages with their own address: module.php and every ViewList key, a view script and a view class, POST actions, redirects and errors, from eZModule and a real extension.
- MongoDB for hosts MongoDB as the database of an Exponential site, from a host's point of view: the PHP, server and extension versions it needs, the Composer library, the database user, installing, the indexes, the documented limits…
- Monitoring overview Everything Exponential offers for watching a hosted site (status commands with exit codes, the system information health checks, log health and the error digest, audit alerts, Velocity's health and metrics endpoints)…
- Namespaces How the template engine keeps variables apart - the root and current namespace, the four ways to name a variable ($var, $ns:var, $:var, $#var), what include does with and without name=, the namespaces section and let…
- Non-profits FAQ Short answers, each with its source, to the questions directors, fundraisers, volunteer coordinators and treasurers of non-profits ask about running their site on Exponential - cost, donations, grants, volunteers…
- Notifications for staff How staff are told about new and changed content on an Exponential intranet - following items, digests, collaboration mail for approvers, the e-mail preferences gate, the notification cronjob and status page, and how to…
- Offline and repeat visits The optional browser navigation cache of Exponential (the service worker /index.js) explained for businesses - faster repeat page visits, the strict rules about what it never stores, the "second view" effect after…
- Order statuses Choosing and writing down your store's status path in Exponential - the seventeen shipped statuses in plain words, which ones your team uses, a status path worksheet, custom statuses, and reviewing the path once a year.
- Owners of several sites: start here For organizations that run several sites, brands or regions from one Exponential installation: what is shared and what is per site, roles per site, cross-site links, staging and production, and the decisions that keep…
- Partner benefits in detail Every benefit of the Exponential Partner Program by level as published - revenue opportunities, visibility, meetings, support, referrals, white label, logos, co-marketing, lead priority, discounts and roadmap requests…
- Past events and the archive What to do with events after they happen on an Exponential site - keep them in a yearly archive, hide them automatically with hide.php on the To Time, remove sign-up data, and publish outcomes such as recordings and…
- PHP and database upgrades Upgrading the platform under Exponential - PHP versions supported, database server versions, the order of steps, staging, and what an in-house IT team or a government cloud provider must coordinate.
- Publishing a FOI response Step by step for editors: turn an answered request for information into a public disclosure log entry with its redacted documents, have it approved, check it as a visitor, and link it from related pages.
- Pull request etiquette The habits that get pull requests merged and make maintainers glad to see your name - small and focused, explained, tested, patient, open to change - and what to avoid.
- Release and upgrade planning How Exponential versions are numbered and published, what the project commits to, and how to plan, schedule and verify an upgrade of a site from any 6.0.x (or older) to the current line.
- Reset a password from the command line Step by step - set a new password for any account, including a lost administrator password, with bin/php/resetuserpassword.php, generating a random password so nothing lands in the shell history.
- Responses, redirects, errors and JSON How a module view answers - the $Result array instead of a Response object, the pagelayout around it, redirects with redirectTo and safe redirect targets, error pages with handleError and eZError codes, JSON and other…
- Restoring to a test server For operations teams in public bodies running a restore test or preparing a copy for acceptance testing. The step-by-step restore of an Exponential site onto a separate machine, with mail stopped, no cronjobs, network…
- Role design: auditors A read-only role for internal auditors, information security officers and records officers - the audit trail by channel, masked logs, role pages and version history - without any right to change content, settings or the…
- Roll back the CSP to report-only Step by step - when an enforced Content Security Policy blocks work, return the siteaccess to report-only in minutes, make every process send the new header, and keep collecting reports to fix the cause.
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