Troubleshoot Letter Manager database errors
Resolve missing table, column or index issues through the module’s portable installer path. 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 goAdmin Area → Setup → Modules → Letter Manager; authorised database diagnostics
Before you start
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What you’ll accomplish
Resolve missing table, column or index issues through the module’s portable installer path. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Follow these steps
- Capture the exact table/column error.
- Verify the active files match v1.0.0.
- Run activation/schema upgrade in a controlled environment.
- Check guarded columns and tables.
- Retest create, send, verify, sign and read tracking.
Fields and options to review
Action scopeResolve missing table, column or index issues through the module’s portable installer path.
Module version1.0.0
Exact routeAdmin Area → Setup → Modules → Letter Manager; authorised database diagnostics
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Rules the system enforces
- Both install.php and runtime helpers can add selected fields.
- Do not repeatedly execute unreviewed ALTER statements directly in production.
How to confirm it worked
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.