Bug 3005 - Record deletion successful
Summary: Record deletion successful
Status: RESOLVED DUPLICATE of bug 5428
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: PC All
: P3 enhancement
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 11:02 UTC by Chris Cormack
Modified: 2019-05-04 19:12 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 01:05:17 UTC


---- Reported by emily.funk@liblime.com 2009-03-04 11:02:29 ----

A library would like to see a success message after deleting a record. Right now it's not obvious the record is deleted. The librarian is taken back to the search screen and until the indexing takes place, the title is still searchable.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:05 UTC  ---

This bug was previously known as _bug_ 3005 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3005

Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here: chris@bigballofwax.co.nz.
   Previous reporter was emily.funk@liblime.com.
CC member arm@hanover.ca does not have an account here

Comment 1 Katrin Fischer 2016-06-19 21:35:30 UTC
still valid.
Comment 2 Katrin Fischer 2019-05-04 19:12:53 UTC
This clashes a bit with bug 5428 that asks for a redirect to the search results after successful deletion. Maybe we could do both, display a success message and do a redirect. I am marking this duplicate of the other and adding a comment there as well.


The point about the title still being searchable might be remedied by the new indexer that makes the index updates almost immediately.

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