Similar to checkin, checkout notices already present. Renewal notices can be set in messaging preferences at borrower and membership category level. Contents will be picked up from a notice template.
Created attachment 5353 [details] [review]
Send Item renewal notice
Version numbers should only be assigned by the RM.
The kohaversion file shouldn't be in this patch and the updatedatabase file
should not say:
+$DBversion = "3.05.00.011";
it should instead say:
+$DBversion = "3.05.00.XXX";
Created attachment 5373 [details] [review]
With update DB version xxx
Created attachment 5781 [details] [review]
This works well for me. The notices were sent correctly upon renewal. I wish item and issue information could be included with the notice but it looks like that's an outstanding issue with other notices as well.
This patch uses GetMemberDetails() universally on every renewal, whether or not a notice will actually be generated. The only bit of information used from this expensive call is the categorycode. It would be better, therefore, to use GetMember() instead, which is a much lighter-weight subroutine and will result in less of a performance hit.
For example, GetMemberDetails() includes a call to patronflags(), which calls checkoverdues(), which pulls in all the biblio, biblioitems (minus marc), items and issues data for every overdue that patron has...
This feature has been implemented by bug 9151.
*** This bug has been marked as a duplicate of bug 9151 ***