Bug 14270 - Software Error: (as_string)
Summary: Software Error: (as_string)
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching (show other bugs)
Version: 3.16
Hardware: PC Windows
: P1 - high critical
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-25 10:40 UTC by Anderson Goes
Modified: 2019-06-27 09:24 UTC (History)
1 user (show)

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


Attachments
this is one study that cause error ! (315.90 KB, image/jpeg)
2015-05-25 10:40 UTC, Anderson Goes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anderson Goes 2015-05-25 10:40:13 UTC
Created attachment 39483 [details]
this is one study that cause error !

hi, 
When you enter for example ( The Louse ) a book name in Brazil , in search field, Koha brings this error message :

Software error :
Can not call method " as_string " on an undefined value at /usr/share/koha/lib/C4/Koha.pm line in 1608 .
For help , please send mail to the webmaster ( [no address given Beheerder ] ) , giving this error message and the team and date of the error .

And I am not able to resolve this error , with other books and authors , even when the base it does not bring me to search information or catalog .

I hope you can help me solve this error as soon as possible !

Grateful !
Anderson Goes
Comment 1 Katrin Fischer 2015-05-25 11:07:02 UTC
Please take a look at bug 12577#c9 - maybe this will help.
Comment 2 Jacek Ablewicz 2015-05-25 12:15:21 UTC
That sounds more like a Bug 12243 (similar effect, i.e. search failing when some records found have invalid ISBNs in them - same cause, only in 3.16 branch it was happening from slightly different reasons). But I think it got already fixed somewere around 3.16.7 release, by patch from Bug 13167 (commit 9990c3e8a1071bc07ffba05950d8c86c95e81064).
Comment 3 Katrin Fischer 2015-05-25 12:16:34 UTC
You are right, thx Jacek!
Comment 4 Jacek Ablewicz 2015-06-24 18:09:43 UTC
Marked as 'RESOLVED', as it is apparently already fixed in current 3.16.x release.