- Contributing back with pull requests Send a fix or feature to the kernel or someone else's extension as a pull request: one change per branch, tests, a description of what was broken and how you checked it, and what to do after.
- Controllers: module views Where a framework has controllers and actions, Exponential has module views - a view script or an Exponential\Runnable\ModuleView class that receives the address parameters and returns a result array - how to write one…
- Copyright and author lines How to write the copyright line of a theme in ezinfo.php, extension.xml, file headers and composer.json - years, holders, earlier authors of a ported or forked design - with real examples.
- Cron and shell access How customers on panel servers schedule Exponential's runcronjobs.php (parts, schedules, the right PHP binary, the site user's crontab), what the administration's Cronjobs page needs from PHP, and what a site can and…
- Data retention and deletion How long an Exponential site keeps logs, audit records, consent records, trash, sessions and form data by default, which settings change it, how to delete data when a person asks, and what stays with you and your host…
- DDoS and probe floods Runbook for a public website under a flood of requests - telling probes from real load with security.log and the error digest, what Exponential does and does not block, keeping the site up with caches, request rules and…
- Declaring compatibility Tell users and tools which Exponential and PHP versions a theme release works with - composer.json require, the README's requirements, extension.xml dependencies and the release notes - consistently.
- Directory sign-in and LDAP What Exponential really offers for signing staff in with company directory accounts - the kernel's LDAP and text file login handlers, how users and groups are created, single sign-on and custom handlers as extension…
- Distributing a theme Publish a theme others can install - licenses of the code, fonts, icons and images it carries, metadata, Composer, content class packages, screenshots and a README - with a checklist before the first release.
- Editors and roles per department How to let each department's editors work only on their own site in a shared Exponential installation: roles limited by subtree or section, one or several administration siteaccesses, shared media, and review of access.
- Environments for development, test and production For public-sector IT teams that keep separate development, test (acceptance) and production copies of an Exponential site. How EXP_ENV gives each machine its own settings, how to keep test copies from sending mail or…
- Extension updates Keeping the extensions of a public-sector Exponential site current - finding what runs and what is outdated, updating with a dry run through ezupdate or Composer, third-party extensions, and the checks after an update.
- Extranet launch checklist Everything to tick before the first partner, customer, dealer or supplier is invited to an Exponential extranet - address and HTTPS, separation tests, registration and approval, sign-in, files, ordering, mail…
- eZContentClass and its attributes Read content classes and their attributes from PHP - fetchByIdentifier(), classIDByIdentifier(), dataMap(), fetchAttributeByIdentifier(), datatype and content - using identifiers, not IDs.
- FAQ: support Answers to the support questions public bodies ask about Exponential - who supports it, free and paid support, response times, SLAs, partners, security reports, and how to ask so you get an answer.
- For loops Counting loops with for: from a number to a number, counting down, sequences, and typical uses such as star ratings, placeholders and page numbers.
- GitHub releases and release notes Turn a pushed tag into a GitHub release - title, notes from the changelog, what to attach and what not - with the gh command and the rule that a published release is never edited to change what it delivers.
- Governance of AI and agents The part of the AI, agents and agentic section for the people who set the rules - privacy and data leaving the site, cost control, the audit trail for AI, roles and least privilege for assistants and agents, and a…
- Hosting and data location requirements Requirement wording for where and how a public CMS is hosted - on premise or by a supplier, data location, databases, operating systems, outbound connections, backups and recovery - with what Exponential's documentation…
- Hosting cost drivers Which technical choices make hosting an Exponential site cheaper or dearer - hosting model, database, engine, number of sites and servers, storage, caching, optional services, backups and staff time - with the facts…
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