Hi everyone,
It's that time again, we're coming up to release time for 24.11 and that
means picking the team for the 25.05 cycle!
Please see the roles page at
https://wiki.koha-community.org/wiki/Roles_for_25.05 and add your name to a
role if you would like to propose volunteering for it. The te
Hi everyone,
We need your help!
I'd like to advertise that we have a vote upcoming in the community for the
roles for the next release cycle, 24.11.
Please see the roles page at
https://wiki.koha-community.org/wiki/Roles_for_24.11 and add your name to a
role if you would like to propose voluntee
Bug 30979 was written to mostly resolve this use case. There are further
enhancements to it reported to limit by IP range and things, but the basics
all work.
If you wanted a specific device required I'd suggest using the code
developed for the above as a starting point.
On Wed, 17 Apr 2024, 2:
That might be what the _NAMES override is for.. I believe you pass it a
list of the Prefs your overriding and it'll then display a message in the
sysprefs if the staff client stating their likely override at the virtual
host level.
On Sun, 18 Feb 2024, 10:21 pm David Cook via Koha-devel, <
koha-de
We use it still I believe. There's an allow list of options inside the
middleware:
https://git.koha-community.org/Koha-community/Koha/src/branch/master/Koha/Middleware/SetEnv.pm#L66
I can't remember what the _NAMES option is for of the top of my head. Let
me know if you need any further guidance a
It's probably context related.. perl and TT can be finicky.
.branchcode is a relation accessor as well as the column name so you may
need to call .branchcode.branchcode (ie the branchcode relation followed by
the same named column in the branches table branchcode.
Finally, your mixing <<>> and [%
