Bug #4157

Server 500 error on multiple record deletion

Added by Jesús García Crespo over 8 years ago. Updated over 7 years ago.

Status:VerifiedStart date:
Priority:CriticalDue date:
Assignee:David Juhasz% Done:

0%

Category:-
Target version:Release 1.3
Google Code Legacy ID:atom-2209 Tested version:
Sponsored: Requires documentation:

Description

To reproduce this error: ========================
On my system, when trying to delete a record with multiple child
records, the server reports an error, and returns a blank page which
when reloaded shows that exactly half (rounded down to the next
integer) of the child records have been deleted. To delete the whole
set of children is therefore a time-consuming iterative process.

See: http://groups.google.com/group/ica-atom-users/browse_thread/thread/ed7e274815cf5941

Resulting error: ================
PHP Fatal error: Call to a member function getTitle() on a non-object
in /var/www/vhosts/.../ica-atom/lib/QubitSearch.class.php on line 421

[g] Legacy categories: Search / browse


Related issues

Related to Access to Memory (AtoM) - Bug #4713: Deleted record still shows in search results, causes 404 ... Verified 02/20/2013

History

#1 Updated by Peter Van Garderen over 8 years ago

  • Priority set to High

[g] Labels added: Priority-High

#2 Updated by Jesús García Crespo over 8 years ago

  • Priority changed from High to Critical

[g] Labels added: Priority-Critical
[g] Labels removed: Priority-High

#3 Updated by Jesús García Crespo over 8 years ago

  • Status changed from New to In progress

See r10794, it could be a fix for this issue.

#4 Updated by MJ Suhonos over 8 years ago

  • Status changed from In progress to QA/Review

#5 Updated by Anonymous over 8 years ago

  • Status changed from QA/Review to Verified

Worked for me!

#6 Updated by David Juhasz over 8 years ago

Also see /p/qubit-toolkit/issues/detail?id=2273. The /p/qubit-toolkit/issues/detail?id=2273.patch file attached to that issue will fix this issue when applied against Release 1.2.

#7 Updated by David Juhasz about 8 years ago

  • Status changed from Verified to In progress

This is still occurring in Release Candidate 1.2.1 despite patches :(

[g] New owner: David Juhasz

#8 Updated by David Juhasz about 8 years ago

I think this is a problem with deleting related QubitRelation objects (lib/model/QubitInformationObject.php lines 293 and 305). The QubitRelation::delete() method then tries to update the search index for the original QubitInformationObject (e.g. http://code.google.com/p/qubit-toolkit/source/browse/trunk/lib/model/QubitRelation.php#120).

#9 Updated by David Juhasz about 8 years ago

Can't reproduce in Qubit trunk, but this is definitely still and issue in Release 1.2.1.

#10 Updated by David Juhasz about 8 years ago

  • Target version changed from Release 1.2.1 to Release 1.3

[g] Labels added: Milestone-Release-1.3
[g] Labels removed: Milestone-Release-1.2.1

#11 Updated by David Juhasz about 8 years ago

  • Status changed from In progress to QA/Review

Please confirm that this is working in trunk

#12 Updated by Jessica Bushey almost 8 years ago

  • Status changed from QA/Review to Verified

Tested with deletion of a record with 53 descendents - works fine.
Tested with deletion of a record with 17 descendents - works fine.

Also available in: Atom PDF