Understand QR-code generation and fallback
This guide explains that how the module represents the secure public URL when different QR libraries are available. 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 → Delivery Note → PDF or public document
What you’ll accomplish
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.
Follow these steps
- Generate a PDF for a note.
- Find the QR or secure-link graphic.
- Scan it with an authorised test device.
- Verify 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 and options to review
- TCPDF native barcode writer where used by the PDF
- phpqrcode candidates
- chillerlan QRCode when available
- SVG secure-stamp fallback based on URL hash
Rules the system enforces
- 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.
How to confirm it worked
- The document retains a safe secure-link representation across supported environments.
Safety checks 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.