Bug 32527 - Can`t print information about staff user in circulation slips
Summary: Can`t print information about staff user in circulation slips
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-23 17:40 UTC by Pablo López Liotti
Modified: 2023-03-08 16:53 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo López Liotti 2022-12-23 17:40:54 UTC
Hi: 

Making customized ISSUESLIP and ISSUEQSLIP, the library circulation staff ask me if it´s possible add the staff user to the slips.

Thinking that <<user>> variable works fine in cataloguing frameworks, by example, 
I added it but did'nt work. Neither [% user %], [% loggedinusername %], [% loggedin_user_name %] and others. 

If <<today>> works, why <<user>> don't ? it's not a global var?

Thks in advance

Pablo
Comment 1 Katrin Fischer 2022-12-27 22:15:45 UTC
The special placeholders available in the frameworks are a completely separate feature to the fields in the notices.

In some notices (ACQORDER for example) these work, but not in slips:

<<LibrarianFirstname>>
<<LibrarianSurname>>
<<LibrarianEmailaddress>>
Comment 2 Pablo López Liotti 2023-03-08 16:20:54 UTC
nobody helps?
Comment 3 Katrin Fischer 2023-03-08 16:53:24 UTC
(In reply to Pablo López Liotti from comment #2)
> nobody helps?

I did reply. <<user>> is indeed not a global var, but just available for the frameworks.

You can find the objects available in the different notices here:
https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit

But bugzilla is for bugs and feature requests - this might actually be better suited for the mailing list. Maybe someone has found a trick to include the information already.