Bug 19964 - Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2438
Summary: Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Bi...
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: PC All
: P5 - low critical (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-12 11:55 UTC by Maria Nunes
Modified: 2019-06-27 09:24 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
3 images as described in comment (164.78 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-01-12 11:55 UTC, Maria Nunes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maria Nunes 2018-01-12 11:55:07 UTC
Created attachment 70464 [details]
3 images as described in comment

This error occurs on records that are data as deleted, but actually appear in the results of an OPAC and Intranet environment search (image 1).
What appears to give rise to these failures is some power failure when creating a new bibliographic record. The record gets an error in some field, does not allow us to have access to continue to edit or correct, but appears in the search results (image 1); and when trying to open this error appears (image 2 & 3).

can anyone help find a solution, especially so that erroneous bibliographic records do not appear in the OPAC and Intranet search results?

Thanks

Maria Nunes
Comment 1 Nick Clemens 2018-01-12 12:45:23 UTC
It sounds like an indexing error - you should run a full rebuild of your indexes to make sure these are all cleared out. 

As to why it happened, that is harder to say. If records were deleted via the db the zebra queue may not have been updated.

You can ask in IRC or on the mailing lists for more information, but I think it is not a bug