There is some code in the serials frequencies template for triggering a JavaScript alert to confirm deletion of a frequency, but it is incomplete. You only get a warning about deleting a frequency which is in use by an existing subscription.
Created attachment 48699 [details] [review] Bug 15981 - Serials frequencies can be deleted without warning A JavaScript alert should ask the user to confirm deletion of a serial frequency. This patch adds this to the template. To test, apply the patch and go to Serials -> Manage frequencies - In the list of frequencies, click any "Delete" link. - Verify that a JavaScript alert is triggered. - Test that cancelling the alert cancels the deletion operation. - Test that confirming the alert allows the deletion to complete.
Created attachment 48817 [details] [review] Bug 15981 - Serials frequencies can be deleted without warning A JavaScript alert should ask the user to confirm deletion of a serial frequency. This patch adds this to the template. To test, apply the patch and go to Serials -> Manage frequencies - In the list of frequencies, click any "Delete" link. - Verify that a JavaScript alert is triggered. - Test that cancelling the alert cancels the deletion operation. - Test that confirming the alert allows the deletion to complete. Signed-off-by: Nicole C Engard <nengard@bywatersolutions.com>
Created attachment 48842 [details] [review] Bug 15981 - Serials frequencies can be deleted without warning A JavaScript alert should ask the user to confirm deletion of a serial frequency. This patch adds this to the template. To test, apply the patch and go to Serials -> Manage frequencies - In the list of frequencies, click any "Delete" link. - Verify that a JavaScript alert is triggered. - Test that cancelling the alert cancels the deletion operation. - Test that confirming the alert allows the deletion to complete. Signed-off-by: Nicole C Engard <nengard@bywatersolutions.com> Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Pushed to Master - Should be in the May 2016 release. Thanks!
Patch pushed to 3.22.x, will be in 3.22.5
This patch has been pushed to 3.20.x, will be in 3.20.10.