PDF generation, branding and files

Troubleshoot Letter Manager PDF generation

Resolve missing files, broken images, unwritable storage or malformed content. 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.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → create/resend test; server → uploads/letter_manager

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 files, broken images, unwritable storage or malformed content. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Verify uploads/letter_manager is writable.
Verify the company logo file exists if expected.
Test with simple subject and plain content.
Check PHP/TCPDF errors and module error logs through authorised diagnostics.
Go to the generated path and verify file permissions.

Fields and options to review

Action scopeResolve missing files, broken images, unwritable storage or malformed content.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → create/resend test; server → uploads/letter_manager

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

PDF output is written before email is attempted.
A missing target email does not explain a missing PDF.
The supplied controller does not wrap the PDF generation sequence in a user-facing exception handler.

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.

Was this guide useful?Your response is stored only in this browser.