From bd0d0e8581d08e0d952deca044d76204bc9f1173 Mon Sep 17 00:00:00 2001 From: Katrin Fischer Date: Mon, 14 Mar 2011 00:08:39 +0100 Subject: [PATCH] Bug 5861: items.stocknumber not saved correctly Content-Type: text/plain; charset="utf-8" The field was missing in Items.pm. It will still act strangely if you enter a stocknumber that already exists in the database. (see Bug 5860) Adding/editing items with stocknumbers you have not used before should work as expected. --- C4/Items.pm | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/C4/Items.pm b/C4/Items.pm index 05df0c5..d293608 100644 --- a/C4/Items.pm +++ b/C4/Items.pm @@ -1897,7 +1897,8 @@ sub _koha_new_item { uri = ?, enumchron = ?, more_subfields_xml = ?, - copynumber = ? + copynumber = ?, + stocknumber = ? "; my $sth = $dbh->prepare($query); $sth->execute( @@ -1934,6 +1935,7 @@ sub _koha_new_item { $item->{'enumchron'}, $item->{'more_subfields_xml'}, $item->{'copynumber'}, + $item->{'stocknumber'}, ); my $itemnumber = $dbh->{'mysql_insertid'}; if ( defined $sth->errstr ) { -- 1.7.1