| Summary: | AUTO_RENEWALS and AUTO_RENEWALS_DGST notices cannot access branch information | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Lucas Gass (lukeg) <lucas> |
| Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | gmcharlt, kyle, martin.renvoize |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Lucas Gass (lukeg)
2022-03-22 22:00:52 UTC
Marking this as resolved because I learned you can use: [% checkout.library.branchname %] (In reply to Lucas Gass from comment #1) > Marking this as resolved because I learned you can use: > > [% checkout.library.branchname %] I wonder where we could document this. At the moment these kind of things make it hard to have libraries modify the TT templates. Maybe it would still be nice to be able to access the branch or library object directly for more consistency? Hm ok, answering my own question... for the DGST the branches might be different... so that object would not work unless we make it the library patrons home branch as in other DGST notices? I wouldn't use 'checkout.', I think in that case it's likely to pick the last checkout, assuming you've placed it after the loop. I'd use patron.homebranch. |