Bug 24743 - Selecting items to delete from the detail.pl page - when deleted provides a message in Error
Summary: Selecting items to delete from the detail.pl page - when deleted provides a m...
Status: RESOLVED DUPLICATE of bug 24423
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: 19.05
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-27 14:32 UTC by Kelly McElligott
Modified: 2020-03-15 17:05 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kelly McElligott 2020-02-27 14:32:27 UTC
This is a confusing one!  

If multiple items need to be deleted from a record.  Koha gives the option to select the items from the holdings tab.  Selecting a few items will provide options in the holdings tab to batch modify or batch delete.  If a library chooses to batch delete these few selected items, Koha brings the user to the Batch Item Deletion Tool.  From here, the items are successfully deleted, however, when Koha gives the success box and allows the user to "Return to the Record" clicking this link - user then gets an alert that the record doesn't exist! The deletion of the items does happen, but Koha is incorrect in alerting that the record doesn't exist because it still does!

Steps:
1. Go to a Detail.pl page of a record that has multiple items
2. Choose a few items in the holdings tab
3. See action buttons- choose to batch delete items
4. In Batch Item Deletion - choose to delete the items.
5. Koha gives Success - # of items deleted.
6. Koha gives link to return back to record
7. Clicking the link  Koha states that "Record Doesn't Exist" (But it does!)
Comment 1 Katrin Fischer 2020-03-15 17:05:41 UTC
I believe this was fixed by bug 24423.

*** This bug has been marked as a duplicate of bug 24423 ***