Understand QR-code generation and fallback
Know how the module represents the secure public URL when different QR libraries are available.
Exact navigationAdmin Area → Delivery Note → PDF or public document
What this guide covers
Know how the module represents the secure public URL when different QR libraries are available. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Exact step-by-step process
- Generate a PDF for a note.
- Locate the QR or secure-link graphic.
- Scan it with an authorised test device.
- Confirm it opens the same secure public note URL.
- If it is a fallback stamp rather than a scannable QR, use the visible/open secure link.
Fields, choices and supported possibilities
- TCPDF native barcode writer where used by the PDF
- phpqrcode candidates
- chillerlan QRCode when available
- SVG secure-stamp fallback based on URL hash
Code-backed validations and workflow rules
- The library catches QR-rendering failures and returns a fallback image rather than breaking the document.
- The fallback stamp communicates secure-link presence but may not behave as a standards-compliant scannable QR.
- The encoded value is the bearer-token public URL.
Expected result and verification
- The document retains a safe secure-link representation across supported environments.
Checks, security and troubleshooting
- Protect printed QR codes because they can grant public access to the note.
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.