https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27919
Katrin Fischer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |additional_work_needed --- Comment #26 from Katrin Fischer <[email protected]> --- 1) Translatability We have untranslatable strings again: + nodes += '<span class="claimed_returned">(Claimed returned)</span>'; For JavaScript inside a .tt or .inc, you need to use the _() syntax. 2) Feature/workflow question For testing, I did the following: * Check out an item * Make the "claim returns" column visible in the checkouts table via table config * Click the button => Nothing happens * Set ClaimReturnedLostValue to a LOST status * Button started working Question: Is this the intended behavior? It looks like this allows to keep an existing lost status, but it still forces you to pick and set one if the item was not lost before. I am happy if that's how it's intended, just bringing it up as a question. * I removed the lost status from the now unlocked item tab form. Question: The item now shows as available in the staff client and the OPAC, although the claim hasn't been resolved in the patron account. Should it be possible to remove the lost status like that or should we only be able to replace it? I am still pushing this, but I am trusting to get some replies and a speedy follow-up for 1)! -- 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/
