Bug 12036 - Neworderempty.pl fails to add items when itemrecorddisplay is too long (acqCreateItem=ordering)
Summary: Neworderempty.pl fails to add items when itemrecorddisplay is too long (acqCr...
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: 3.14
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-03 11:45 UTC by Marcel de Rooy
Modified: 2017-06-14 22:12 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

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel de Rooy 2014-04-03 11:45:30 UTC
In 3.14.4 I encounter this problem in Acquisition, neworderempty.pl:

The output of PrepareItemrecordDisplay (called by itemrecorddisplay.pl in additem.js [cloneItemBlock]) seems to be too long.
The line $(clone).append(data) in the ajax success function in cloneItemBlock fails silently.
This makes it impossible to add items to a new empty order when AcqCreateItem=ordering.

Did anyone else see that already or solved it? 
(I created the ACQ framework by just copying from Default.)
On a clean master I could not reproduce this problem, but it seemed that the output of PrepareItemrecordDisplay was around 23000 there instead of 27000 chars.
Comment 1 Marcel de Rooy 2014-04-03 12:44:47 UTC
From IRC:

Joubu	marcelr: It works for meI added some subfields to my ACQ framework. itemrecorddisplay.pl?frameworkcode=ACQ returns 38098 chars and the form is correctly displayed
Comment 2 Jonathan Druart 2015-04-28 08:21:32 UTC
Marcel, do you still have this issue?
Comment 3 Marcel de Rooy 2015-05-04 09:38:53 UTC
(In reply to Jonathan Druart from comment #2)
> Marcel, do you still have this issue?

Normally, I do not have AcqCreateItem set to ordering. So I did not see it recently. But no proof of a solution yet :)
Comment 4 Jonathan Druart 2016-08-16 14:43:52 UTC
Marked as resolved, please reopen if the issue still exists.