Understand public token routes and compatibility
This guide explains that which public paths are implemented and why the generated helper URL should be preferred. 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 goUse the secure link generated on the Delivery Note admin page, email or PDF
What you’ll accomplish
Know which public paths are implemented and why the generated helper URL should be preferred. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Copy the generated secure link from the note detail page.
- Test it in a private browser session.
- Verify the public view loads and the signing form posts to the supported sign route.
- Use configured route options only through an authorised deployment process.
Fields and options to review
- Default view route option: delivery_note/public_view
- Default sign route option: delivery_note/public_sign
- Compatibility hyphen and controller aliases in routes.php
- Query-token controller form used by current email/sign view
Rules the system enforces
- Public-route helper rejects unsafe aliases and values containing `admin/`, then falls back to defaults.
- The live README notes underscore URLs are preferred for the target SaaS router.
- Do not use `dead_public_*` methods as active endpoints.
How to confirm it worked
- Generated links resolve through the route/controller arrangement supported by the installed build.
Safety checks and troubleshooting
- Do not hand-build a URL that exposes an incorrect controller path or drops the token.
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.