Open ChurchCRMBugReport opened 3 years ago
Attached is an example report ChurchCRMFormattingProblem.pdf
Still problematic - here's an image from version 4.5.4
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Still a problem.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
@dleigh I feel like PDF reports can be a common issue because of all of the edge cases.
How would you feel if these reports were webpages instead?
That's an interesting thought. I'm guessing that we wanted to be able to send people a PDF with the results via email so that they could give us their feedback. But sending them an HTML email or even an email with a link to a unique web page would be fine by me. The way it is now is unusable and I'd pick usable over that any day. Thanks!
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 15 days with no activity.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
I don't think the fact that it goes over 2 pages is particularly helpful either.
And the English one has issues too:
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Many of the labels, but also content, wraps outside of its boundry boxes and creates a nearly unreadable report that we can't use for verification. Not sure what the best solution is, but my guess is that the attempt to create a "nicely formatted" report is going to fail when the values fall outside of the bounds of the "nice formatting".
My suggestion would be that a simple table of "field label: value" pairs be output or at least that it could be an option if the formatted style breaks for a given language.