| Summary: | Order receiving error | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Govind Basedia <librarian> |
| Component: | Acquisitions | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | erin.arnold, hagud, kdembek |
| Version: | 22.11 | ||
| Hardware: | PC | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Error in order receiving | ||
Can you get to your server's log files maybe? The 500 is only what we see in the interface, the real interesting information will be hiding there. Same problem in 23.05.04 Hi Govind, is it the same data you are testing with in both versions? The order receive process has been changed a lot between 22.11 and 23.05. We need more information here to be able to help. Please check your browser logs for any JS issues and the server logs for any other error occuring. Good morning, I have suffer the same issue...
I have checked that this only happens in some orders, then it must be some metadata issue (my point of view)
I have dumped database and restored in koha 23.11 and worked fine...caming back to 22.05
I have checked logs in koha 22.05.*
[2024/01/05 01:18:13] [ERROR] GET /api/v1/acquisitions/orders: unhandled excepti on (Mojo::Exception)<<Can't call method "to_api" on an undefined value at /usr/s hare/koha/lib/Koha/Biblio.pm line 1098.>> Koha::REST::Plugin::Exceptions::__ANON __ /usr/share/koha/lib/Koha/REST/Plugin/Exceptions.pm (73)
I suspect it is an issue with metadata of the orders, checimg the code
sub to_api {
my ($self, $args) = @_;
my $response = $self->SUPER::to_api($args);
my $biblioitem = $self->biblioitem;
I suspect it could be the biblioitem data, not presented in some recordS?
I have added a else condition to ignore if there is no biblioitem
I have edited the code and add a log warn [2024/01/05 01:43:10] [WARN] Biblio with biblionumber 13250 does not have a valid biblioitem object at /usr/share/koha/lib/Koha/Biblio.pm line 1108.
And it works... I can confirm that there is no biblioitem with that biblionumber.. then it is a metadata issue
If you have entries in your biblio table without a matching entry in the biblioitems table, that would be a serious data issue. What else I could imagine is that your biblionumbers and biblioitemnumbers got out of sync. Could you check if biblionumber = biblioitemnumber in your biblioitems table? Most of the time that is the case as we have a 1:1 relationship, but through migration etc. things can get out of synch sometimes. We are seeing this error in 23.05.08 Thanks for looking into it! This happens to me in 23.05.09 if the items were not given an item type during the acquisitions process. Once I go to the record and give them an item type, they'll suddenly appear in the receiving search results. (In reply to Keith Dembek from comment #7) > This happens to me in 23.05.09 if the items were not given an item type > during the acquisitions process. Once I go to the record and give them an > item type, they'll suddenly appear in the receiving search results. Hi Keith, this is the expected behavior. Koha now expects all items to have an item type. It's not only order receive, but also the OPAC display that will break otherwise. One solution could maybe be assigning a temp item type by batch editing all items without. |
Created attachment 157967 [details] Error in order receiving I am using koha version 22.11.10.when receiving order something went wrong when loading the table 500 internal server error please see the screen shot.