Summary: | Crash on item tab of a record with UNIMARC | ||
---|---|---|---|
Product: | Koha | Reporter: | Victor Grousset/tuxayo <victor> |
Component: | Staff interface | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
Severity: | blocker | ||
Priority: | P5 - low | CC: | gmcharlt, jonathan.druart, joonas.kylmala |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32747 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35896 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Victor Grousset/tuxayo
2022-09-08 16:38:59 UTC
I cannot get any biblio to show even, or search for them with kohadevbox and after having ran "reset_all_unimarc". We are not checking whether the item in question has an itemtype. Need to add a check for that. Patch coming right up. Actually, do we require itemtypes? If not, then at least the regression is caused by Bug 24185: Make holds page faster: Preparatory refactoring >+ Koha::ItemTypes->find( $i->effective_itemtype() )->notforloan and bug 27272 related dependencies. So after grepping for Koha::ItemTypes->find I can see almost all places in Koha expect there to be an itemtype to be defined. Koha just doesn't want to work without itemtypes, and for some reason the unimarc default data seems to come without itemtypes linked to the items. Putting back to NEW status. Need to discuss first how to proceed. Unfortunately we don't seem to have foreign key constraint from items table to itemtypes table, so these errors are bound to happen. Thanks for the analysis :)
> unimarc default data
Is that just about sample data that is inserted directly via SQL? Or is that something that valid UI usage can produce?
This looks like a data problem from misc4dev. You should report the problem there (which I won't fix myself however). For anyone coming here, the problem has been reported in this ticket gitlab DOT com/koha-community/koha-misc4dev/-/issues/76 |