https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30303 --- Comment #10 from Brendan Lawlor <blawlor@clamsnet.org> --- (In reply to Lari Taskula from comment #8)
This is so cool!
Thanks Lari!
I noticed that after merging, if I hit the browser's back button, it takes me back to the field selection where I am once again able to select the fields to retain. Surprisingly, the new choices would still apply after hitting "Merge" the second time, even if Koha says "No valid patrons to merge were found.". But in some sense this feels more like a feature than a bug, because I might have forgotten to select something and this allows me to correct my error.
This is sort of just the nature of the browser using a web app like Koha. Different browsers may behave differently too. I understand how in this case it could be confusing though. I think this might be better handled on the server side with HTTP Cache-Control headers like no-cache, no-store or must-revalidate, but this could also be done with javascript to force a reload when the browser's back button is used. I'm not sure if it's necessary, but the last patch forces a reload when you use the back button like this: // Stop the back button loading from cache window.onpageshow = function (e) { if (e.persisted) { window.location.reload(); } } -- You are receiving this mail because: You are watching all bug changes.