Time Nick Message 05:48 reiveune hello 07:11 magnuse__ \o/ 08:36 cait good morning #koha 08:38 krimsonkharne[m] good morning! 09:11 paulderscheid[m] hi #koha 09:11 * cait waves 09:11 cait all German here this morning :D 09:13 cait but the others will hopefully join soon 09:56 ashimema morning 09:57 ashimema Kann ich mitmachen? 09:59 Joubu join koha-non-german 10:00 ashimema lol 10:14 cait just happy to no longer be the only one :) 10:15 cait morning Joubu and ashimema 10:15 Annelisterman[m] been here all morning but silent :D Ich spreche schlecht Deutsch. 10:19 cait *hides* 10:31 cait can I come out again? 10:32 Annelisterman[m] yes please :D 10:38 tiagosimoes[m]1 Hello, can anyone see this message? 10:39 cait thanks :) 10:39 cait tiagosimoes[m]1: yes, we can read you 10:39 tiagosimoes[m]1 oh good, I thought I was talking to void again 10:40 tiagosimoes[m]1 so uh, I have an issue with Koha's searching functionality (namely that isn't showing any results when I do a search). Is it ok if I ask here or is there a more appropriate place to get help? 10:41 cait it's perfectly ok 10:41 cait some questions to start with: Are you using Zebra or elasticsearch for searching? has it worked before? 10:43 tiagosimoes[m]1 Zebra. Yes, this is in a testing environment and I have both an older version of Koha (18.05) and Debian (9 aka stretch), which I updated recently to 10 in this testing environment. Everything went fairly well but yeah, no results are showing up when I do a search. 10:43 tiagosimoes[m]1 In "About Koha", it also tells me Zebra server appears to not be available. Is it running? 10:44 tiagosimoes[m]1 Btw, I'm not an IT person, just a librarian with an interest in computer science and Linux experience. So apologies if I don't understand the more technical terms 10:44 tiagosimoes[m]1 Anyway, I tried the following:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/hQJDaCTGKrpbLbXpSkArVqgo>) 10:47 cait ok 10:47 cait ry to start it 10:47 cait sudo koha-zebra --start instance 10:47 cait where instance is the name of your library's instance you created 10:48 cait tiagosimoes[m]1: ^ 10:48 tiagosimoes[m]1 will do, thanks 10:51 tiagosimoes[m]1 alright, done 10:53 cait did it help? 10:53 tiagosimoes[m]1 no :(. About Koha still outputs the same message 10:54 cait if you do a sudo koha-zebra --stop and the start after... any useful output? 10:54 tiagosimoes[m]1 will try that 10:55 tiagosimoes[m]1 no, nothing 10:55 Joubu Don't you want to upgrade to a newest (and supported) version of Koha? 10:56 tiagosimoes[m]1 Yes, I do. First I'll update Debian and then Koha 10:57 Joubu I would update first, then try to fix the problem. Maybe you are fighting a bug that has been fixed. 10:57 tiagosimoes[m]1 but I was told to first try it in a testing environment and to not jump version 10:57 Joubu why not? 10:57 schnydszch when paying fine, we are getting error 500 in Koha 23.11. error is: [2024/01/25 18:01:19] [WARN] Use of uninitialized value $CGI::Compile::ROOT::usr_share_koha_intranet_cgi_2dbin_members_pay_2epl::change_given in concatenation (.) or string at /usr/share/koha/intranet/cgi-bin/members/pay.pl line 81. 10:57 schnydszch [2024/01/25 18:01:26] [WARN] DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Column 'issue_id' cannot be null at /usr/share/koha/lib/Koha/Object.pm line 170 10:58 schnydszch is this a bug? Thanks in advance! 10:58 Joubu dump the DB, reinstall Koha with 23.05 (or even 23.11), insert the dump, restart everything 10:58 Joubu tiagosimoes[m]1: dump the DB, reinstall Koha with 23.05 (or even 23.11), insert the dump, restart everything 10:58 Joubu schnydszch: version of Koha? 10:59 Joubu sorry, 23.11 11:00 tiagosimoes[m]1 Joubu: But in the production environment, it's working correctly. 11:00 tiagosimoes[m]1 We already have a bunch of unresolved issues from earlier versions, wouldn't that add a ton of other potential issues? 11:01 Joubu @later tell schnydszch `show create table accountlines` should show "`issue_id` int(11) DEFAULT NULL" - it can be null 11:01 huginn` Joubu: The operation succeeded. 11:02 tiagosimoes[m]1 tiagosimoes[m]1: > <@tiagosimoes:matrix.org> But in the production environment, it's working correctly.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/bHKkvVKfdcVYNegjprSfEksF>) 11:02 Joubu tiagosimoes[m]1: zebra is supposed to work out of the box, especially with new versions. It seems easier to upgrade than investigate a problem on an old version. 11:03 Joubu what kind of issues? 11:06 tiagosimoes[m]1 Some of them do seem to be bugs, like, when you search for a specific authority in the Authorities module on the staff interface and there's more than 1 page, they're duplicated in the second page. We also seem to be having trouble with printing labels from Koha with special characters 11:06 tiagosimoes[m]1 I haven't investigated this thoroughly so they could just be bugs fixed in the newer versions 11:08 tiagosimoes[m]1 Unfortunately I can't be 100% dedicated to managing Koha so I haven't had the time to check those issues. 11:08 tiagosimoes[m]1 But I suppose I can try upgrading to 23.05 in the testing environment and see how it goes. Should I upgrade Debian as well? 11:09 Joubu ideally, yes 11:10 tiagosimoes[m]1 So, first upgrade Debian and then Koha? Or it doesn't matter much? 11:11 Joubu yes, first upgrade the OS 11:13 tiagosimoes[m]1 alright, I'll give it a shot. Thanks @Jou 11:14 tiagosimoes[m]1 alright, I'll give it a shot. Thanks @_oftc_Joubu:matrix.org and @_oftc_cait:matrix.org 11:32 oleonard o/ 11:48 ashimema didn't fancy double checking my follow-up on bug 33457 did you owen? 11:48 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33457 minor, P5 - low, ---, oleonard, Signed Off , Improve display of fund users when the patron has no firstname 11:48 ashimema oleonard ^ 11:49 ashimema I reckon we can PQA if you agree with it 11:49 oleonard Oh yeah I saw that you added something. I will take a look. 11:50 ashimema cheers 11:51 ashimema LOL 11:52 ashimema i just spotted it could be simplified even further! 11:52 tcohen morning #koha o/ 12:01 oleonard ashimema: Are you reworking or should I go ahead and test? 12:02 ashimema I'm done 12:02 ashimema there are two follow-ups on the bug now ๐ 12:03 ashimema we can squash them if you confirm they work as expected.. I tested quickly and was happy, but it's good to get that second pair of eyes on a followup like this 12:15 Joubu ashimema: on top of the modal bug maybe? 12:15 Joubu shouldn't it be done for other searches as well? 12:16 ashimema I was thinking this was a simple backport and it's a bug... all be it trivial 12:16 ashimema yes, it should 12:16 ashimema we need that modal bug in ๐ 12:21 * oleonard is trying to decide if we need a modal WRAPPER bug before the Bootstrap 5 upgrade... 12:25 ashimema is this OPAC or Staff? 12:25 ashimema there aren't too too many modal in the opac as yet... 12:25 ashimema but there are loads in staff 12:25 ashimema have fun 12:29 Joubu oleonard: what's your opinion on bug 35864? bug or ft? 12:29 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35864 enhancement, P5 - low, ---, koha-bugs, In Discussion , Should we clear patron search result when the modal is reopened? 12:30 Joubu "we need a syspref" is not a valid answer :D 12:30 oleonard :) 12:32 oleonard It's a tough question. Right now it doesn't clear patron search results, correct? I think we should leave it that way for now. 12:32 marcelr o/ 12:32 Joubu indeed, it does not for now 12:38 marcelr Joubu: running UNIMARC btw? 12:40 marcelr in the context of 19097 12:44 Joubu nope 13:26 cait another day not going as planned :( 13:27 marcelr planning++ 13:28 tcohen cait: you are awesome, don't put pressure on you too much 13:30 tcohen Joubu: around? 13:45 tcohen anyone else seeing this? https://snipboard.io/WjLyAO.jpg 13:46 caroline My console is empty on the main page 13:50 paulderscheid[m] tcohen yes always 13:50 paulderscheid[m] Might be platform dependent 13:56 tcohen thanks paulderscheid[m] 13:56 tcohen my Vue errors didn't allow me to see it, and now I fixed those, I thought it was some other mistake I made :-P 13:58 paulderscheid[m] It only affects firefox, though 14:00 Joubu tcohen: seeing it for months, yes 14:28 oleonard-away tcohen: https://github.com/FortAwesome/Font-Awesome/issues/19925 14:32 schnydszch Joubu++ 14:33 schnydszch Joubu, thanks for the hint! :) 14:50 caroline while more people are around, can someone check the order of the reply-to? In the AcquisitionsDefaultReplyTo syspref, it says "If left empty, it will fall back to the first defined address in the following list: library reply-to, library email, ReplytoDefault, KohaAdminEmailAddress" 14:51 caroline But I thought it was library reply-to, ReplytoDefault, library email, KohaAdminEmailAddress, because the library reply-to says it fallsback to ReplytoDefault, not the library's email 14:52 ashimema looking 14:52 caroline thanks ashimema++ 14:53 caroline I was writing the order for the return-path (library's return-path, ReturnpathDefault, library's email, KohaAdminEmailAddress, if I understand correctly) and stumbled on that list and it confused me 14:55 ashimema if left empty.. it leaves it empty.. which means it'll follow the normal fallback pattern 14:55 ashimema ah.. but this is 'SendAlerts' which does whatever it fancies 14:57 caroline the normal fallback pattern being ReplyToDefault before the library's email, or the opposite? 14:57 ashimema right 14:57 ashimema if it's not set.. it'll look at 'ReplytoDefault' 14:59 ashimema and ONLY ReplyToDefault 14:59 ashimema I don't see any further fall through 15:00 caroline seems to me like a bug 15:01 ashimema the whole of C4::Letters is a bug ๐ 15:01 caroline lol! 15:01 ashimema I keep saying that.. but whenever I try to get interest in fixing it I get nothing back 15:01 caroline I thought it was KOha::Email now 15:02 ashimema notices and letters are a nightmare of inconsistencies.. and people keep adding crap to them 15:02 ashimema only a very small part of it 15:03 caroline If it's something testable from the interface, you can cc me to test 15:03 caroline If it's code refactoring, i'm not much help though 15:05 caroline So conclusion to my question is *It depends*? 15:06 ashimema no, no depends 15:06 ashimema it only falls back to ReplyToDefualt 15:06 ashimema nothing else 15:06 caroline specifically AcquisitionsDefaultReplyTo 15:07 ashimema AcquisitionsDefaultReplyTo -> ReplyToDefult -> Nothing 15:07 caroline But in general, the order depends on the letter? 15:07 ashimema yes 15:08 caroline ok that's good to know 15:08 caroline I'll write a bug report to either change the order or change the test of the syspref for that one at least 15:08 ashimema good to know.. bad for code 15:08 ashimema ๐ 15:12 caroline should I create like an omnibus for all the replyto's and then a specific bug for each? 15:12 marcelr i hope not :) 15:13 marcelr dont forget the 'current behavior' guys too 15:13 caroline There is SerialsDefaultReplyTo too, which was added ad the same time, might have the same problem 15:13 ashimema nope 15:13 ashimema that one is the same.. 15:13 ashimema sorry.. I mean yes.. that one is the same 15:14 caroline the syspref give the whole list, so that is untrue also 16:06 reiveune bye 16:34 saa in koha even after deleting biblio, items why still records are still searched with details 16:35 cait probably your koha-indexer isn't running? 16:35 saa though it gives error the record you requested does not exist 16:35 cait the index is cleaned when deleting records if things are working properly 16:35 cait it sounds like it#s still in the search index, but was deleted from Koha 16:35 cait indexing problem 16:35 saa how can i check and correct 16:37 saa but when i run koha-rebuild-zebra -f -v it does not show any records 16:37 saa but still records are searched 16:38 cait you are missing the instance 16:39 saa no added instance when running command 16:39 cait yes, that should work and reset... unless you have no records at all? 16:39 cait if your database is empty the index might not reset 16:39 saa i wondering from where data is still stored 16:40 saa is there any way to empty these records 16:40 tcohen what SearchEngine are you using? 16:41 saa zebra 16:41 tcohen ok 16:41 tcohen do you have records on your DB? 16:41 tcohen what is you Koha version? 16:42 saa 23.11.01 16:42 saa i dont see records in db 16:43 saa but on staff client i can search 16:43 cait the search index is a different thing to what is iny our db 16:43 cait it's not in the db. 16:43 saa only when i try to click on title it throws error the record you requested does not exist 16:43 saa how can i then clear searchindex 16:44 cait the result list is drawn from thes search index, that was not reset/deleted, the detail page checks the db and gives you an error 16:44 cait the easiest is probably: add a record 16:44 cait and reindex if that doesn't help 16:44 saa ok let me check 16:45 cait there is also this: https://koha-community.org/manual/latest/en/html/faq.html#reset-the-zebra-index 16:45 saa but i think there should be a way to empty records 16:48 saa tx cait that helped by resetting zebraindex 16:48 saa thanks a lot 16:48 saa i have one more query how can i disable public access to my koha staffclient 16:49 cait that's a sysadmin question 16:49 cait you could use a firewall to limit access to certain ip addresses 16:50 cait the ip setting for branches shoudl do a similar thing in Koha, but you might also want to think about solving it on a server level 16:51 saa ip settings for branches i had tried but it didnot work properly 16:51 cait I believe there might be a bug 16:51 saa ok 16:52 saa if i get correct way it would help me 16:52 saa to setup restricting access to staffclient through google 17:41 oleonard Anyone around who is familiar with using Mana with serials? 17:42 caroline vaguely 17:43 oleonard Based on the template there seems to be two different versions of Mana search results... One from the "Search on Mana" link in the Serials sidebar menu, and another...somewhere? 17:45 caroline when creating the subscription? 17:47 caroline https://snipboard.io/gzERd1.jpg 17:47 caroline Afficher les rรฉsultats de Mana -> Show Mana search results 17:47 caroline Sorry, I didn't think to change my interface 17:47 oleonard No problem, my Duolingo streak is strong :) 17:48 caroline +1 17:48 oleonard I will try to get a match! 17:49 caroline I searched for National Geographic France, but any Nat Geo is probably there 18:07 oleonard Thanks caroline 18:07 caroline np! was it what you were looking for? 18:07 oleonard Yep. I couldn't see it because I'd introduced a JS error on the page :| 18:08 caroline oops! 18:59 davidnind BibLibre++ 18:59 davidnind ^^ Reached 25 employees in 2023 https://piaille.fr/@biblibre (in French) 19:03 JosephLamb[m] Hello, after updating to 23.11, when I search for a book, there are no results. But there are items when I do an item search. I go to the OPAC page and I search for a book and nothing returns. I have rebuilt the zebra index. But I did not reboot or restart services. Where should I start to look for the problem? Thank you 19:08 oleonard JosephLamb[m]: I don't know how to advise you, but I can say that what you describe sounds like a problem with Zebra. Item search is a different kind of search, that's why it works. 19:11 JosephLamb[m] Is this similiar to saa's problem above? 19:11 oleonard Could be! 19:13 davidnind Joseph Lamb: The two common resolutions I've noticed with Zebra issues are 1) Restarting services (I would definitely try that) 2) Permission issues with the index files on the server (I don't know any more than that, so hoping others can offer some advce) 19:16 JosephLamb[m] So the problem was I had to rebuild the index. But then I needed to restart the services. I did not have that in my notes. 19:16 JosephLamb[m] zebra index 19:19 davidnind normally when you do a full reindex you shouldn't need to, but after doing an upgrade it is probably a good idea 19:23 JosephLamb[m] Thank you for your help. davidnind 19:24 JosephLamb[m] and oleonard . thank you 19:26 davidnind glad that you were able to solve the issue! 19:30 davidnind @later tell saa Definitely look at either firewall rules or Apache server configuration to restrict access to the staff interface. It's not something I'm familiar with, but it is a pretty common thing to do as part of hardening web services. Also, as cait said there is a bug with the AutoLocation system preference and using the library specific IP field, a fix is being worked on - thanks for helping identify it! 19:30 huginn` davidnind: The operation succeeded. 19:32 JosephLamb[m] oleonard: Is the item search a mana search? Or what is the search engine? 19:32 caroline JosephLamb[m], it's just an SQLq query 19:32 oleonard It's a direct SQL query of the database tables 19:33 davidnind caroline++ 19:33 davidnind oleonard++ 19:33 JosephLamb[m] ok 19:34 caroline davidnind++ isn't it early for you? 19:37 davidnind 8:30am ish here - have just been getting up later lately... 19:38 caroline oh ok, that's reasonable! I thought it was like 5am or something :) 19:46 davidnind 5am is always a struggle for me, between 6-7 am is typical (except maybe for Winter time...) 19:50 JasonGreene[m] has anyone converted from an old system called Handy Library Manager made by PrimaSoft in the 90s into a new Koha system? 19:55 davidnind Jason Greene: There is a relatively recent thread on the Koha General Mailing list - maybe you are the same Jason? https://lists.katipo.co.nz/pipermail/koha/2021-April/056086.html 19:59 JasonGreene[m] That is probably me... I'm asking because we have made the move, yet my boss is seeing some missing data. He wants the Koha to get "patron data and item-level data" from Handy Library Manager... and I'm trying to find out how 20:00 caroline item-level data is usually in the marc records, if that system can export in marc 20:01 JasonGreene[m] it can't export to marc because it is not marc.. We had to convert it using MarcEdit 20:01 caroline you'll have to map the fields in the handy library to fields in Koha. In MARC21, we use the 952 field for all item information (in UNIMARC it's 995 I think) https://koha-community.org/manual/latest/en/html/cataloging.html#location-and-item-information-952 20:02 caroline oof, ok! I've had to work with systems like that 20:03 caroline So the boss says there is missing data, are you able to extract that data from handy library? 20:03 JasonGreene[m] Handy Library Manager exports these field ( ID TYPE CATEGORY ISBN TITLE AUTHOR CALL BARCODE ) 20:05 JasonGreene[m] I sent Primasoft a support email and asked them ... we'll see the answer soon 20:06 JasonGreene[m] Just asking others to see if anyone was able to get that data 20:06 caroline I never had that one, so I can't say, sorry 20:09 JasonGreene[m] That's ok, I'll keep looking. If we can't then we'll have to build a new Koha server and enter all items by hand :-( 20:14 davidnind Maybe you could use the inventory tool or a report, then identify anything missing that way (I've never used it, so not sure if it is a viable solution - would depend on how many items you have!) 20:14 caroline I know I'm preaching to the choir, but I hate that data can be stuck in a software... :/ 20:15 tcohen mtj: you introduced HTTP::Tiny in the cpanfile, to force a minimum version 20:15 tcohen is that right? 20:16 tcohen people are seeing the modules page report they need an upgrade, so our repo is not providing new enough one? 20:30 davidnind caroline: 100% (I think that should be a top selection criteria for any software organisations use - often they are just focused on the features or solving the problem they can see - sometime in the future they will most likely need to change, and need to get their data out (but this will generally be "someone else's problem!")) 20:32 JosephLamb[m] I would like to add email notifications to Koha. I am using a gmail account. But the email failed to send. This is at my home lab and there are no firewall rules outbound. Is there a better service to use. I did not install postfix. 20:34 caroline did you configure the smtp with gmail info? 20:37 davidnind Joseph Lamb: This is how I configure the testing environment that the community uses (KTD) to send email when testing, not sure whether this is robust enough for production or whether there are limits - https://gitlab.com/-/snippets/1893788#user-content-enabling-email-for-testing-the-easy-way 20:37 davidnind you also need to enable email for your instance https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#Email 20:38 davidnind I think there is a setting under Koha administration where you can smtp servers if your organisation has one or a service available 20:38 cait there might be some imitations with gmail, I remember some posts to the list 20:45 JosephLamb[m] <caroline> "did you configure the smtp..." <- Yes 20:48 JasonGreene[m] <davidnind> "Maybe you could use the inventor..." <- We have about 18000 books 21:41 davidnind Jason Greene: That's a decent size, it would be a reasonably-sized inventory exercise!