The "Cancel" link (which only displays if there is an error) also breaks when placing multiple holds at once from a list. Example URLs that are generated for the links.
These links are generated using [% CGI.param('redirect_to') || CGI.referer | html %] - it looks like CGI.param('redirect_to') is what is causing the array link that doesn't work. If I delete that and just use CGI.referer, the links are valid, but they're still not ideal because they only go back to the previous page (the hold form) rather than to the list (which is two pages back).
If I replace CGI.referer with javascript:history.go(-2); then it goes two pages back and takes me to the list (this also still works when placing single holds from the search results page or record details page) as I expect it to, but that requires javascript to be enabled in the browser so it's not ideal either.
The "Cancel" link (which only displays if there is an error) also breaks when placing multiple holds at once from a list. Example URLs that are generated for the links.
CANCEL: /demo.evergreen catalog. com/eg/ opac/ARRAY( 0x7fc20b49f148)
https:/
CONTINUE: /mlnc2. noblenet. org/eg/ opac/ARRAY( 0x7f55a88dcf98)
https:/
These links are generated using [% CGI.param( 'redirect_ to') || CGI.referer | html %] - it looks like CGI.param( 'redirect_ to') is what is causing the array link that doesn't work. If I delete that and just use CGI.referer, the links are valid, but they're still not ideal because they only go back to the previous page (the hold form) rather than to the list (which is two pages back).
If I replace CGI.referer with javascript: history. go(-2); then it goes two pages back and takes me to the list (this also still works when placing single holds from the search results page or record details page) as I expect it to, but that requires javascript to be enabled in the browser so it's not ideal either.