Troubleshoot public Delivery Note signing failure
Diagnose token, status, CSRF, browser and signature-data branches safely.
Where to goSecure public Delivery Note link, then Admin Area → Delivery Note → View note
What this guide helps you do
Diagnose token, status, CSRF, browser and signature-data branches safely. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Verify the link includes the exact token and opens the intended note.
- Check the note is Open, not Signed or Void.
- Verify JavaScript and Signature Pad CDN load in the recipient browser.
- Verify a non-empty signature is drawn and submitted.
- Check the CRM CSRF configuration/token when enabled.
- Check `sign_failed` events and application logs.
- Retest with a controlled open note without changing production data.
Fields and options
- Secure token
- Status
- Signature hidden field
- CSRF token when available
- Browser JavaScript/CDN
- Database update affected rows
Rules and limits
- Missing, invalid and void tokens follow separate error branches.
- Already signed notes reject another sign attempt.
- The model records a signature only when a non-empty value updates the row.
- The code captures IP/user agent and sends confirmation only after success.
Check it worked
- The cause is resolved or clearly identified while the note remains open or sealed according to its actual state.
Safety checks and troubleshooting
- Never force status or insert a fabricated signature to close a support ticket.
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.
Related guides
Was this guide useful?Your response is stored only in this browser.