https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36272 --- Comment #1 from Magnus Enger <magnus@libriotech.no> --- Relevant code in koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/itemsearch.tt: $("body").on("click", "#barcodesExportLink", function(e){ e.preventDefault(); exportItems('barcodes'); }); function exportItems(format) { let item_search_selections = JSON.parse( localStorage.getItem("item_search_selections") ) || []; if (item_search_selections.length > 0) { var href = '/cgi-bin/koha/catalogue/item-export.pl?format=' + format; href += '&itemnumber=' + Array.from( item_search_selections ).join('&itemnumber='); location = href; } else { $('#format-' + format).prop('checked', true); $('#itemsearchform').submit(); $('#format-html').prop('checked', true); } } Export to CSV has the same problem. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36272 Andrew Fuerste-Henry <andrewfh@dubcolib.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrewfh@dubcolib.org, | |nick@bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36272 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #2 from David Cook <dcook@prosentient.com.au> --- (In reply to Magnus Enger from comment #0)

The solution is probably to do a POST, not a GET?

In this case, I'd say that's probably the answer. A little while ago, when working on the CSRF stuff, I think there was a dogmatic decision to do all "read" actions as GET only, but obviously that's not practical in cases like this. (I mean alternatively a "batch" could be created in the database so that the GET could just take that batch ID but that has other logistical difficulties.) I don't know what the community wants to do about cases like this anymore... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36272 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=27859 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36272 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blawlor@clamsnet.org --- Comment #4 from Brendan Lawlor <blawlor@clamsnet.org> --- There are instances of cud-export and cud-form, which makes sense to me to use in cases like this for scalability. I came across this in bug 27248 and decided for cud-form because it uses the post data to fill the form in the template. Maybe this needs to be officially agreed on and then added to the coding guidelines under the CRSF section or somewhere else for clarification. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.