https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42715
Pedro Amorim (ammopt) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |, [email protected], | |[email protected] | |o.uk, | |[email protected] | |k, [email protected] --- Comment #1 from Pedro Amorim (ammopt) <[email protected]> --- Regular fresh ktd, install en-GB (don't enable, just install): 1) Enable ILLModule, create 1 ILL request, visit: http://localhost:8081/cgi-bin/koha/ill/ill-requests.pl?method=create&backend=Standard 2) Pick a type, a cardnumber e.g. 42 and a destination library. Create. 3) Artificially set this request's status to CHK, run: $ koha-mysql kohadev $ update illrequests set status = 'CHK' where illrequest_id = 1; 4) Visit the ILL list: http://localhost:8081/cgi-bin/koha/ill/ill-requests.pl 5) Refresh a few times, notice the status is always 'Checked out'. 6) Set 20 plack workers: $ sed -i 's|<plack_workers>2</plack_workers>|<plack_workers>20</plack_workers>|' /etc/koha/sites/kohadev/koha-conf.xml 7) Install en-GB translation and restart plack: $ koha-translate --install en-GB --dev kohadev $ koha-plack --restart kohadev 8) Repeat 5. Notice you sometimes get 'Issued', other times you get 'Checked out'. 9) Bonus: Install fr-FR, also without enabling it, and refresh: You'll now sometimes get 'Prêté' instead of 'Checked out' or 'Issued'. It's picking up a random installed translation on every new page load, even without enabling - or selecting - that particular language. I believe different plack workers are picking up different installed languages and API requests where $interface == 'api' get confused. It's much less noticeable (or can't reproduce at all) if we keep the stock 2 plack workers. My current leads: 1) strings_map in ILL/Request.pm use of cache may be part of the problem. 2) the 'else' in C4::Languages::getlanguage where interface is neither 'staff' or 'opac' is somehow picking up all installed languages regardless if enabled or not? 3) Plan to consider a x-koha-interface HTTP header and have kohaTable make use of that? Could fix the problem but only by working around it. I've explored all of the above but got nowhere and have unfortunately ran out of time here. Any thoughts are welcome! -- You are receiving this mail because: You are the assignee for the bug. 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/
