Exponential / Download / Modules
Modules (Module Extensions)
Modules are the pages of Exponential that have their own address: content/view, user/login, the shop, the layouts editor and every screen of the administration. An extension adds modules of its own, and since 6.0.15 every module view is a class that a site can extend without copying a file. This page explains modules and views, where to find ready-made ones, how to add and enable one, how to write your own in minutes with a wizard, and where to get help.
On this page
| Section | What you find there |
|---|---|
| Modules and views | How an address becomes a page |
| The kernel's modules | What Exponential brings out of the box |
| Module views as classes | What changed in 6.0.15, and why it matters |
| Where to find modules | The Extensions directory, Exponential Projects, GitHub |
| Add and enable a module | Install the extension, activate it, give people access |
| Write your own module | The module wizards and the step-by-step guides |
| Get help and support | Documentation, community, and paid development from 7x |
Modules and views
Every address of an Exponential site names a module, one of its views and the view's parameters. The address /content/view/full/2 runs the view view of the module content with the parameters full and 2; a friendly URL like /recipes is translated to such an address before it runs.
A module is a folder with a module.php that lists its views and, for each view, the script that runs it, its parameters, the buttons its forms may post and the policy functions a user needs. Policies are what roles grant, so every view of every module can be opened to some people and closed to others without a line of code.
| Part | What it does |
|---|---|
| module.php | Declares the module's views ($ViewList) and its policy functions ($FunctionList) |
| A view | Reads its parameters, does the work, and returns a page: content rendered by a template, and the path for the breadcrumb |
| Templates | Render the view's result in the design of the siteaccess, so a theme can restyle a module without touching its code |
| Policy functions | The permissions of the module, granted to users and groups through roles, with optional limitations by section, subtree or class |
The kernel's modules
Exponential 6.0.15 registers 41 kernel modules in its settings. Among them:
| Module | What it is for |
|---|---|
| content | Viewing, creating, editing, translating and publishing content, versions, the trash, bookmarks and URL management |
| user, role, section | Accounts, sign-in and security, roles and policies, sections |
| class, state, workflow, trigger | Content classes, object states and the workflows that run on events |
| setup, settings, visual | System pages, caches, extensions, the RAD tools, settings and the template editor |
| shop, rss, search, notification, collaboration | The web shop, RSS feeds, search, notifications and approval |
| migration, audit, apikey, graphql, staticpublish | Content migrations, the audit log, personal API keys, the GraphQL endpoint and static publishing |
Extensions bring many more: the Exponential Layouts editor, the newsletter, tags, the Git Manager, the database source editor and the AI writing assistant are all modules of extensions. On the installation that serves this website, the extension point survey counts 679 module views in all (November 2026).
Module views as classes
Since Exponential 6.0.15 every kernel view, command and cronjob part is a class, and new views in extensions are written the same way. The view file named in module.php becomes one line that hands over to the class:
<?php return \Exponential\View\Kernel\Content\History::main( __FILE__, get_defined_vars() );
Why it matters for you:
- Extend a kernel view without copying it. Subclass the view, change what you need, register the subclass in one setting. The next release updates the original underneath your subclass.
- Share code between the web and the command line. A view, a console command and a cronjob part can call the same service class, so the work is written and tested once.
- Test a view without a web request.
- Listen around a view: before and after events fire around every run, so an extension can act on any view.
[RunnableSettings] Implementation[Exponential\View\Kernel\Content\History]=acmeHistoryView
Old view scripts keep working: nothing forces an existing extension to change. The whole story, with the class hierarchy and the scope a view receives, is in Module views as classes. An extension can even replace a whole kernel module: An extension can replace a kernel module.
Where to find modules
| Where | What you find |
|---|---|
| Exponential Extensions directory | Maintained extensions with their composer require line, for example the Git Manager (web-based Git and backups) and private messaging |
| Exponential Projects | The community's project forge. Its historical catalog alone lists 121 module projects, with 102 view and 22 template fetch function projects next to them; each project has downloads, a forum and its Git source. |
| github.com/se7enxweb | The source of every extension 7x maintains, ready to read as working examples |
Older modules were often written for PHP 5. Read them for ideas, check the versions they support, and look for a maintained fork first. All the places to look, and how to judge what you find: Exponential Software (Extensions).
Add and enable a module
A module arrives with its extension, so adding one is the extension routine plus one step for access:
- Install the extension with Composer: composer require se7enxweb/<package>, then php bin/php/ezpgenerateautoloads.php -e.
- Activate it under Setup > Extensions, or in [ExtensionSettings] ActiveExtensions[] of settings/override/site.ini.append.php, and clear the settings cache.
- Give people access: in the roles and policies of the administration, add the module's policies to the roles that should use it. Administrators have every policy already.
- Open it at /<module>/<view>. An extension module can also add a tab or a menu entry to the administration.
The extension registers its modules itself, with one line in its settings:
[ModuleSettings] ExtensionRepositories[]=mysite_hello
Every folder under extension/mysite_hello/modules/ is then a module: /hello/world/Ada runs the view world of the module hello with the parameter Ada. Details: Modules and views and Policy functions and access checks.
Write your own module
You do not start from an empty file. Setup > RAD in the administration has wizards that write a working module and show every file before they write it:
- the Module wizard: a module with views and policies, in a new or an existing extension;
- the Module table wizard: a new database table with its persistent class, schema, administration pages, policies, fetch functions and JSON endpoint, installed from the browser;
- View for an existing module: one more view in a module you already have.
The Module wizard (Setup > RAD): name the extension and the module, describe the views and their policies, read the preview of every file, then create the module.
The Module table wizard: an extension, a module and a database table with its fields, written as a working module with its class, schema, administration pages and policies.
Then follow a guide:
- With RAD: a module with views, reading what the wizard wrote.
- Write your first module view: an extension with a module, a view as a class, a template and a policy, step by step.
- View parameters, unordered parameters and POST, for forms and actions.
- eZModule and module results, the reference.
- Contribute extensions back, when your module is ready for others.
Modules are one kind of extension. See also Themes and designs for the look of your site, and Plugins and extension points for datatypes, template operators, workflow events and event listeners.
Get help and support
| Step | Where | When |
|---|---|---|
| 1. Read the documentation | doc.exponential.earth: the Extension development book and the PHP developers' guide. 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 module built or upgraded for you |

