Summary: | Ability to limit AutoEmailNewUser to specific patron categories | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | g.newman, gmcharlt, kyle.m.hall, lmstrand |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Christopher Brannon
2016-02-16 21:49:56 UTC
I think it's not send if you leave either email, username or password empty - maybe something to try as a work around. But would be nice to have this as an option by patron category. Yeah, kind of a clunky workaround, if you remember. Options are always better than workarounds. Agreed. The preference has since been renamed, but I think the enhancement request is still very valid. It seems the WELCOME notice supports template toolkit. https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit List of available variables states branch, borrower. One could write an if-else block to check if a borrower's category matches a value and place the message inside the block. Empty messages are not sent if I'm correct. This counts as a workaround too though, I guess. (In reply to Lari Strand from comment #5) > It seems the WELCOME notice supports template toolkit. > https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit > > List of available variables states branch, borrower. > > One could write an if-else block to check if a borrower's category matches a > value and place the message inside the block. Empty messages are not sent if > I'm correct. > > This counts as a workaround too though, I guess. If Template Toolkit had solid and complete documentation for notices, then yes, a workaround. But even if documentation for TT in notices were solid, the average user doesn't have basic programming skills. TT isn't doesn't even have a ready set of insertable elements like the outdated hungry alligator elements/fields that are still present. If we are going to rely on TT for basic needs, then we are a bit short sighted for the average library that doesn't have someone that knows how to program at that level, and we are offering no easy way to implement it. I guess the question is, what things are common enough to put built in functionality for, and what things are out of the scope of average use and should be left to TT? Lari, I think your workaround should work. I also documented this on the wiki a little while ago: https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit#Don.27t_generate_e-mail_for_a_patron_category |