Recent changes
Wednesday November 04 2026
-
Debugging extensions Updated Markdown page
A routine for an extension that does nothing or breaks a page: is it active, are its settings read, do its classes load, are caches or workers stale, with the RAD health check, checkclasses and the logs.
-
A design inside an extension Updated Markdown page
Templates, overrides, stylesheets, scripts and images an extension carries: which design folder to use, how to make them overridable, and how they reach the page.
-
Documenting your extension, including help pages Updated Markdown page
Document an extension where people look: README.md and INSTALL.md on top, the rest as Markdown in doc/, in English; the help center shows it while the extension is active, with front matter, featured pages and context…
-
Events, listeners and filters Updated Markdown page
React to the kernel without changing it: ezpEvent, [Event] Listeners[], notify versus filter events, the events the kernel announces, and the rule that a filter returns its value.
-
The extension directory layout Updated Markdown page
Every folder and file name an extension can have, what the kernel does with it, which setting points the kernel there, and how many of the installed extensions use it - the map for the rest of Part 3.
-
Extension load order Updated Markdown page
Which extension wins when two provide the same setting or template: the written order of ActiveExtensions, how declared dependencies reorder it, extra extension folders, and how to see the real order.
-
extension.xml: metadata and dependencies Updated Markdown page
The extension.xml file: the metadata read before ezinfo.php, and the requires, uses and extends dependencies that the Extensions page shows and that decide the loading order.
-
ezinfo.php: who made it and which version Updated Markdown page
The ezinfo.php metadata file - class name, the static info() method, the keys the administration reads, how it is read after extension.xml, the PHP 8 bare-key trap with a real fix, and how to check it.
-
Fetch functions Updated Markdown page
Let templates fetch your data: function_definition.php, the collection class and its result array, a verified example, fetch aliases, and extended attribute filters for content fetches.
-
Handlers named by settings Updated Markdown page
Replace one part of the system with a class chosen by a setting: getHandlerClass(), a verified mail transport, and the handler points for login, session, search, shop and more.
-
Kernel class overrides: the last resort Updated Markdown page
Replacing a kernel class through the override autoload map: how it works, what it costs, the wizard and its drift check, and the lighter mechanisms to try first.
-
Modules and views Updated Markdown page
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.
-
Performance in extensions Updated Markdown page
Keep an extension fast and safe under persistent workers: count queries, fetch with limits, cache, keep listeners cheap, measure, and never keep request state in statics.
-
Persistent objects and your own tables Updated Markdown page
Your extension's own table through eZPersistentObject: definition(), create, store, fetch, lists with conditions and limits, count, remove, template attributes, transactions.
-
Policy functions and access checks Updated Markdown page
Protect a module: policy functions and limitations in module.php, views that require them, eZUser::hasAccessTo() with its yes, no and limited answers, and granting through roles.
-
Security in extensions Updated Markdown page
The security rules every extension follows: policies on views, POST and form tokens, escaping, safe SQL, untrusted input, safe redirects, files, secrets and no inline code.
-
Settings in an extension Updated Markdown page
Settings an extension ships: registration lines in kernel INI files, your own INI file with documented defaults, reading it safely with eZINI, per-siteaccess settings and secrets.
-
Facts, themes and logos for the system card Updated Markdown page
How an extension adds its own facts to ./console exp:expfetch, exp:info and exp:about - a provider class (expSysCardProvider, expSysCardBaseProvider), syscard.ini ProviderClasses[], a test with a fake context, a theme…
-
Template functions Updated Markdown page
Block tags like {mysite_card}...{/mysite_card}: registration, the process() contract, evaluating parameters and children, a verified example, and when an operator or include is better.
-
Template operators Updated Markdown page
Give templates new operators: the registration, the four methods the engine calls, named parameters and piped input, a complete verified example, testing, and the PHP 8 pitfalls.