Understand module enabled and invoice UI options
Distinguish the master module-enabled control from the optional invoice-page interface flag. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goNo staff-menu settings screen exists in the supplied code → Review installed Delivery Note options
What you’ll accomplish
Distinguish the master module-enabled control from the optional invoice-page interface flag. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Verify `delivery_note_enabled` is `1` for live use.
- Verify `delivery_note_invoice_ui_enabled` is `1` when invoice-page buttons and the new-invoice panel should appear.
- Test the module register separately from invoice-page injection.
- Change options only through an authorised deployment/configuration process because the supplied module has no settings form.
Fields and options to review
- delivery_note_enabled
- delivery_note_invoice_ui_enabled
Rules the system enforces
- When disabled, module hooks stop adding menus and assets.
- Invoice assets load only on invoice editor pages and only when the invoice UI option is enabled.
- The module register and module pages are scoped separately from invoice UI injection.
How to confirm it worked
- The intended module and invoice-page interfaces appear without loading module assets globally.
Safety checks and troubleshooting
- Do not describe these options as clickable CRM settings; no such user-facing settings screen is implemented.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.