https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13547
--- Comment #9 from Christopher Brannon <[email protected]> --- (In reply to Katrin Fischer from comment #8) > This patch works as expected, but there is a little catch: For libraries, > that have used this field to add information that is patron privacy relevant > (like the name of someone), this change might be problematic. I have seen > this happening, as the field will show up on checkout/checkin in a prominent > way. (When returned, hand over to X next or something like that). > > Even when the materials column is hidden, it's still fully visible in the > source code. > > Would it be possible not to pass it to the template if the column > configuration is set to not display it? Is it fair to withhold this functionality because some might be using it for something it wasn't intended for? How many other fields are used in a similar fashion? I can understand this caution on a field that was meant to hold sensitive information, but I am not sure about this one. Maybe it could be suppressed with column configuration, but unless we treat other fields the same way, this suppression might get lost in future upgrades because it doesn't coincide with other column practices. -- 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/
