https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34472
--- Comment #13 from Katrin Fischer <[email protected]> --- (In reply to Christopher Brannon from comment #12) > Hmmm....that makes no sense to me. So if I were to create a new Overdue > Notice with a completely different code, I wouldn't be able to use the > template toolkit objects associate with it because I didn't use a specific > code? It works for overdue, but it's not the code or the module, but because you configure it in the notice triggers. The system knows it's an overdue and pulls the data accordingly. > This seems ripe with potential issues down the road. It seems like the TT > objects should be associate with the module, not a code. Otherwise, that > would be a nightmare for custom notices down the road. > Does that make any sense, or am I just out of my mind? I'd say they are more tied to the function that generates the notice/slip. Some features allow you to configure the code to use like overdues, some are tied to a specific code and some to a specific module. I expect us to not be overall consistent right now as the code doesn't use the module to determine the objects available in general. For an examples: Bug 29100 - Add checkouts data loop to predue/due notices script (advance_notices.pl) Changed the advance_notices script to make the checkouts object available to TT, but only for the notices sent by this script, not for all in circulation module. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
