1. put «damaged: 1» in the syspref 2. in OPAC search something that yield at least on result with a least one item 3. error Can't use string ("1") as an ARRAY ref while "strict refs" in use at /kohadevbox/koha/C4/Items.pm line 1012 staff interface search is okay
I think this is invalid with bug 28125.
The about page warning is not likely to be found when hitting the issue. But that can still help. And we have other fish to fry. If somebody wants to make it easier to find the cause the OPAC search crash, they can send a patch here. Anyway, «damaged: 1» doesn't trigger the warning ^^"
filter_by_visible_in_opac and GetHiddenItemnumbers have different behaviours: From GetHiddenItemnumbers: if (any { $val eq $_ } @{$hidingrules->{$field}}) { Expect an array (damaged: [1]) From filter_by_visible_in_opac: { '-not_in' => $rules->{$field} } will work for array and scalar GetHiddenItemnumbers must be removed anyway.
This is no longer valid since bug 23583. *** This bug has been marked as a duplicate of bug 23583 ***
(In reply to Jonathan Druart from comment #3) > filter_by_visible_in_opac and GetHiddenItemnumbers have different behaviours: > > > From GetHiddenItemnumbers: > if (any { $val eq $_ } @{$hidingrules->{$field}}) { > Expect an array (damaged: [1]) > > From filter_by_visible_in_opac: > { '-not_in' => $rules->{$field} } > will work for array and scalar This is true: it is an unadvertised side-effect of considering the OpacHiddenItems syspref YAML, and not just a subset of YAML.