Bug 12378

Summary:	addbiblio.pl error when deleting record
Product:	Koha	Reporter:	Ian Palko <library>
Component:	Cataloging	Assignee:	Galen Charlton <gmcharlt>
Status:	RESOLVED DUPLICATE	QA Contact:	Testopia <testopia>
Severity:	major
Priority:	P5 - low	CC:	fridolin.somers, gwilliams, jesse, jonathan.druart, m.de.rooy, sfayle, ztajoli
Version:	Main
Hardware:	All
OS:	All
See Also:	http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11817
Change sponsored?:	---	Patch complexity:	---
Documentation contact:		Documentation submission:
Text to go in the release notes:		Version(s) released in:
Circulation function:

Description Ian Palko 2014-06-06 01:34:33 UTC

When deleting a record using the menu on the detail.pl page, "normal" tab, the biblio is successfully deleted, but this is followed by a web page showing:
---------
Software error:

Can't call method "title" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 838.
----------

Previously after deletion of the biblio, koha would return to the advanced search page.

After upgrading to 3.16 it is repeatable everytime an biblio is deleted.

Comment 1 Owen Leonard 2014-06-09 17:47:13 UTC

*** Bug 12390 has been marked as a duplicate of this bug. ***

Comment 2 Owen Leonard 2014-06-09 17:59:03 UTC

I suspect this might be related to (a duplicate of?) Bug 11817

Comment 3 HB-NEKLS 2014-08-27 02:25:29 UTC

I have successfully recreated this bug under this condition: 

If you are on a detail.pl page without items attached (AND in the URL after the bibnumber, this appears: &searchid=scs_1409106045128 (random number), which means you have a return to search results link/previous/next links for a record search) with an empty bib record, and attempt to delete the record (go to Edit --> Delete record), this error message appears. The record has been deleted successfully, but instead of returning to the advanced search page, you get the "can't call method "title"...." error message. 

Owen, it's definitely related to Bug 11817. 

I've been trying to track this bug's cause down for months, and finally saw it happen consistently!

Comment 4 Jonathan Druart 2014-11-04 10:05:31 UTC


*** This bug has been marked as a duplicate of bug 11817 ***