Prepare Letter Manager upload storage
Provide writable storage for generated PDFs, signature images and optional email enclosures.
Exact navigationServer filesystem → CRM root → uploads/letter_manager
Before you begin
- 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 this guide covers
Provide writable storage for generated PDFs, signature images and optional email enclosures. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Confirm uploads/letter_manager exists and is writable by PHP.
- Confirm the web-server user can create PDF and signature files.
- Send a test letter and verify Letter_{reference}.pdf is created.
- Sign a controlled letter and verify {hash}_signature.png is created.
- Attach an enclosure and confirm uploads/letter_manager/enclosures is created and writable.
Fields, choices and supported possibilities
Action scopeProvide writable storage for generated PDFs, signature images and optional email enclosures.
Module version1.0.0
Exact routeServer filesystem → CRM root → uploads/letter_manager
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Code-backed validations and workflow rules
- The installer creates uploads/letter_manager with mode 0755 when absent.
- The enclosure helper creates uploads/letter_manager/enclosures at runtime.
- Stored enclosure files are chmod 0644 after upload.
Expected result and verification
- 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.
Important code-backed limitationGenerated PDFs and enclosure files are stored below the web root in the supplied implementation. Apply server access rules and retention controls appropriate to the sensitivity of correspondence.