Plugins (Extensions)
In Exponential, a plugin is an extension that hooks into one of the kernel's extension points: a new kind of field, a template operator, a workflow event, an event listener, a login handler, a payment gateway. There is no separate plugin system to learn: extensions are the plugin mechanism, and Exponential documents every point they can use. This page explains the main kinds of plugin, how to see every extension point your installation has, where to find ready-made plugins, how to write your own with a wizard, and where to get help.
On this page
| Section | What you find there |
|---|---|
| Plugins are extensions | One mechanism for everything, and why that keeps updates safe |
| The main kinds of plugin | Datatypes, template operators, workflow events, events and more |
| Events, listeners and filters | React to what the kernel does, or change a value on its way |
| Every extension point, on one page | Setup > RAD and the extension point survey |
| Where to find plugins | The Extensions directory, Exponential Projects, GitHub |
| Write your own plugin | Wizards that write the code, and the guides behind them |
| Get help and support | Documentation, community, and paid development from 7x |
Plugins are extensions
Exponential has no separate plugin format. Every addition, from a single template operator to a complete page builder, is an extension: a folder under extension/ and a Composer package. What makes an extension a plugin is that it registers code at one of the kernel's extension points, nearly always with a line in its own settings:
[ExtensionSettings] ActiveExtensions[]=myplugin
Once the extension is active, its settings are read together with the kernel's, and the kernel finds the datatype, operator, listener or handler they name. Nothing in the kernel is edited, so an update of Exponential never overwrites your plugin, and switching the extension off removes it cleanly.
The main kinds of plugin
| Kind | What it adds | Guide |
|---|---|---|
| Datatype | A new kind of field for content classes, with its own storage, validation, edit form and view | Write a datatype |
| Template operator and template function | New words for the template language, from formatting a string to fetching data | Write a template operator |
| Fetch function | Data a template can ask for with fetch(), with the module's permissions applied | Write a fetch function |
| Workflow event type | A step that runs when content is published, a user signs in or an order is placed: approval, notification, payment, anything | Write a workflow event type |
| Event listener and filter | Code that reacts to a kernel event, or changes a value on its way through the kernel | Below |
| Console command and cronjob part | Work that runs from the command line or on a schedule | Write a console command, Write a cronjob part |
| Handlers | Login and single sign-on handlers, payment gateways, shipping and VAT handlers, search plugins, binary file handlers, database drivers: classes the kernel picks by a setting | Extension points from PHP |
| Module | New pages with their own address | Modules |
| Design | A theme, or templates that override others | Themes and designs |
Events, listeners and filters
The kernel announces what it does through its event hub, and an extension listens. There are two kinds of event:
- Notify: your listener is told that something happened (a view cache was cleared, a session ended, an image size was made). Its return value is ignored.
- Filter: your listener receives a value, for example the rendered page before it is sent or an access decision, and returns it, changed or not.
A listener is one line in the extension's settings, the event name and the method to call. The kernel's own form token protection is written this way:
[Event] Listeners[]=request/input@ezxFormToken::input Listeners[]=response/output@ezxFormToken::output Listeners[]=session/regenerate@ezxFormToken::reset
Events are also sent before and after every module view, console command and cronjob part, so a plugin can act around any of them. The events the kernel sends, the rules for filters and how to send your own: Events, listeners and filters.
Every extension point, on one page
You do not have to search the code for the place to plug in. The administration has two pages for it:
- Setup > RAD describes 74 extension points in seven groups (content; templates and design; modules and views; workflow, events and jobs; storage and infrastructure; packaging and shop; users, access and language). For each it names the mechanism, the setting that registers it and the documentation, and 68 of them have a wizard that writes the code.
- The extension point survey counts everything your installation actually registers at those points, and lists every entry that cannot work: a class that does not exist, or a replacement that does not extend the class it replaces.
On the installation that serves this website, the survey counted 7,192 registrations on 11 November 2026, among them:
| Registered at | Count |
|---|---|
| Template overrides | 3,219 |
| Settings that name a class (handlers, datatypes, operators and more) | 1,219 |
| Commands, cronjob parts and views as classes | 701 |
| Module views | 679 |
| Template operators and functions | 518 |
| Places the kernel looks for handlers | 335 |
| Policy limitations | 287 |
| Interfaces and abstract classes to implement | 120 |
| Events | 64 |
The numbers depend on what is installed: every extension you add raises them, and the survey on your own installation shows yours.
Setup > RAD in the administration: the extension points written up and those with a tool, the survey's headline, and the points in groups, each with its mechanism and a button that opens its wizard. The counts are those of the installation the screenshot was taken on.
The extension point survey: what the installation registers at each point, from settings that name a class to module views and events, and the entries that cannot work.
The same catalog, as a page of the documentation: Extension points at a glance. The mechanisms behind it, and how to choose the lightest one: Extension points from PHP.
Where to find plugins
| Where | What you find |
|---|---|
| Exponential Extensions directory | Maintained extensions with their composer require line, among them a Stripe payment gateway, the str_replace template operator, custom tags that embed YouTube, Vimeo and Spotify content, and automatic RSS feeds by workflow event |
| Exponential Projects (also at plugins.exponential.earth) | The community's project forge. Its historical catalog alone lists 73 datatypes, 71 template operators, 38 workflow event types, 27 template functions, 9 payment gateways and 8 login handlers, each with its downloads, forum and source |
| github.com/se7enxweb | The source of every extension 7x maintains: working examples of every kind of plugin |
The addresses plugins.exponential.earth and plugin.exponential.earth open Exponential Projects as well. Many of the historical plugins were written for PHP 5: read them for ideas and look for a maintained fork before you install one. All the places to look: Exponential Software (Extensions).
Write your own plugin
Pick the extension point on Setup > RAD, open its wizard, fill in the names, read the preview of every file, and let it write a working extension. Then change the generated code to do what you need.
The template extension wizard (Setup > RAD): name the operators and functions, describe their parameters, read the preview, and get a working template extension with its settings.
- The RAD tools tour: every wizard in one walk.
- With RAD: a template operator in five minutes and With RAD: a workflow event.
- The chapters on datatypes, template operators, workflow event types and events and filters in the free Extension development book.
- Kernel class overrides: the last resort, for the rare case no extension point fits.
- Contribute extensions back, when your plugin is ready for others.
Plugins are one kind of extension. See also Themes and designs and Modules.
Get help and support
| Step | Where | When |
|---|---|---|
| 1. Read the documentation | doc.exponential.earth: the extension development book, the PHP developers' guide and the reference. The same help is built into the administration. | First, always |
| 2. Ask the community | The forums of Share Exponential, the Telegram support chat, and the forum of each project on Exponential Projects | A question the documentation does not answer |
| 3. Paid development from 7x | Exponential support and the Exponential Support and Development Network: feature development, custom solutions and long-term maintenance | When you want a plugin built or upgraded for you |


