https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30657
Andrew Fuerste-Henry <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Passed QA --- Comment #62 from Andrew Fuerste-Henry <[email protected]> --- Testing: - created non-repeatable attribute UNCLE - created repeatable attribute NICKNAMES - Gave a patron one UNCLE and two NICKNAMES - added to ISSUESLIP: [% FOREACH n IN borrower.extended_attribute_values.NICKNAMES %] [% n %]<br> [% END %] - added to ISSUEQSLIP: [% borrower.extended_attribute_values.UNCLE %] - confirmed both notices generate successfully - edited UNCLE attribute, making it repeatable - reloaded quick slip, it generates successfully, includes "ARRAY(0xaaaafc29aef8)" instead of the attribute value - edited NICKNAMES attribute, making it non-repeatable (note that Koha would not let me make this change until I removed the second NICKNAME value from my patron) - reloaded issue slip, it generates successfully, displays the attribute value I don't think it's a blocker that I end up with the ARRAY printing to my notice if I put a repeatable attribute in my notice without treating it as a list. I similarly end up with a HASH printing in my slip if I just put in [% checkouts %]. I'm setting this back to PQA because the notice successfully generates and therefore no scripts/processes will die if a repeatable attribute is not treated as a list. I'm fully in favor of whatever follow-ups folks can think of to make this even easier for users. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
