Bug 5861: items.stocknumber not saved correctly
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. [F. Demians] Was able to reproduce the bug on an UNIMARC DB. The patch works. Signed-off-by: Frédéric Demians <f.demians@tamil.fr> Signed-off-by: Chris Cormack <chrisc@catalyst.net.nz>
This commit is contained in:
parent
5f7b1a58f0
commit
15126b1108
1 changed files with 3 additions and 1 deletions
|
@ -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 ) {
|
||||
|
|
Loading…
Reference in a new issue