Display conditions
Assign reusable condition sets to a module to control when it shows. A set contains groups and rules (match ALL/ANY, with NOT), and rules can nest other sets. There are 22 rule types across menus, visitor (user group, access level, language, device, OS, browser, IP), date/time (date, day, month, time, season), content (page type, article, category, tag), and other (component, template, URL). Value pickers load live site data.
Conditions are evaluated fail-closed: a module with an unassigned or incomplete condition set cannot “leak” onto the page — if the rules do not positively match, the module is hidden.
Per-module options
- Pre / Post HTML — markup injected around the module output.
- Hide if empty — suppress a module that renders nothing.
- Admin note — a private reminder shown in the list.
Bulk tools & override
Assign or remove conditions in bulk, and mirror or copy assignments between modules. Turn on Override Module Manager (in the plugin settings) to have the core module-manager list redirect to the AMM; every editing screen still uses core.
Managed module provisioning (install / update)
On install and on every update the platform provisions the modules it owns, without disturbing the rest of your site:
- By name only, no wildcards. The package touches only its own managed modules, matched by name — it never bulk-edits other modules.
- Best position by default. Each managed module is placed in its best position for the Mokonyx admin template.
- Minimum one of each. At least one instance of each managed module is enforced on every update, so a module can never go missing.
- Secure access by default. New modules are created at the Registered access level; the Login module is intentionally left Public.
- Your changes stick. If you change a managed module’s access level or position, the update process will not revert it.