One somewhat benign, somewhat jarring behavior in Fill PDF at the moment is that the end user sees errors they have no way of resolving. These should be replaced with a more generic message such as, "An unexpected error has occurred, and the administrator has been notified. If the error persists, provide them with error code (something or other)."

And then log the detailed message to watchdog. And document the error codes somewhere so they're searchable.

Comments

wizonesolutions’s picture

Tagging.

wizonesolutions’s picture

Issue tags: +fillpdf2

Still needs attention, and I have to look at the whole error handling workflow as part of the refactor anyway, so that would be a good time to knock this one out.

liam morland’s picture

Category: Task » Feature request
Issue summary: View changes
Issue tags: -fillpdf2
liam morland’s picture

Version: 7.x-1.x-dev » 8.x-4.x-dev

Features need to be added to 8.x after which they can be backported.

liam morland’s picture

Title: Fill PDF Service errors are exposed to user » FillPDF Service errors are exposed to user
Component: User interface » FillPDF Service
Status: Active » Closed (won't fix)