There is a JavaScript error on the overdues report page. FireBug reports: YAHOO.widget.DS_XHR is not a constructor /cgi-bin/koha/circ/overdue.pl Line 126 This bug blocks Bug 5014 because without a working autocomplete I don't know if the markup corrections I think are required to fix 5014 will break the autocomplete.
Created attachment 8203 [details] [review] Bug 5180: FIX autocomplete on overdues report - Switch off the CircAutocompl syspref - Set a (one or more) patron attr type searchable - go on the overdues page Firebug crash and a layout problem appears on the left. Firebug error is "YAHOO.widget.DS_XHR is not a constructor" retry with this patch.
Is this still an issue? I can't seem to replicate it based on the description on the patch.
(In reply to comment #2) > Is this still an issue? I can't seem to replicate it based on the > description on the patch. I can't reproduce it either. Owen, still relevant ?
Created attachment 8464 [details] [review] [SIGNED-OFF] Bug 5180: FIX autocomplete on overdues report - Switch off the CircAutocompl syspref - Set a (one or more) patron attr type searchable - go on the overdues page Firebug crash and a layout problem appears on the left. Firebug error is "YAHOO.widget.DS_XHR is not a constructor" retry with this patch. Signed-off-by: Owen Leonard <oleonard@myacpl.org>
Yes, this is still an issue in master, and the test plan is the same as what I'm seeing. This patch disables the autocomplete when CircAutocompl is turned off, which may not be what everyone would expect. Perhaps CircAutocompl should be officially transformed into a global switch for autocomplete? jQueryUI will certainly make it easier to add more instances of it.
QA comment : I can't reproduce the issue. However, it's a tiny patch, the code is correct and sound logical. There should be something specific in the configuration I can't reproduce. However, Jonathan and owen confirm the problem exist and the patch fixes it, I have no problem after applying the patch, so passed QA BREAKING NEWS: just 2sec before hitting "save", jonathan suggested something, now I can reproduce the problem = the attribute must be searchable and linked to an authorised value
This bug will be included in the Koha 3.6.5 release.