http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3482 --- Comment #2 from Jane Wagner <jwagner@ptfs.com> 2009-11-25 20:22:01 --- Some hints on how we run these -- the overdues cron is set up as overdue_notices.pl -t -html /tmp/noticedir -itemscontent issuedate,date_due,title,barcode,author (We wanted to use only certain item fields in our notices, so we specified itemscontent fields in the cron entry; that's not a requirement for the feature.) The command line needs to specify a web-accessible directory where the print notices will go -- they get a filename like notices-2009-11-24.html (or holdnotices-2009-11-24.html). The overdue notice itself can be formatted to fit a Z-mailer. Within the notice file, the text is spaced down or over to where it will print properly on the form. The script has code that wraps around the notice file to tell the HTML to obey the formatting, and to do a page break between notices. That's so that when staff print it out, they get one per page. We had to add an extra syspref (PrintNoticesMaxLines) to specify page length because our client allows a _lot_ of checkouts which meant some notices were running onto multiple pages. That syspref says to truncate the print notice at that page length and put in a message about go check your OPAC account for the full list. The print and email overdues use the same notice file. The print notices for holds are different -- there's a separate HOLD_PRINT notice file and the system uses it if there's no email address. Then a nightly cron job runs to gather those up from the message queue and put them in an HTML file in the notice directory, as above. The cron entry is gather_print_notices.pl /tmp/noticedir -- Configure bugmail: http://bugs.koha.org/cgi-bin/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.