Attempting to merge user in collections provides an unfriendly error message

Bug #914800 reported by Michael Peters on 2012-01-11
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Low
Unassigned

Bug Description

Evergreen 2.1.1
Postgres 9.1
Debian Squeeze

When attempting to perform a patron merge on a user who is in the collections status fails, with a network error, instead of a user friendly error message explaining why the merge failed.

The staff member is presented with:

Error Message.
Please open a helpdesk ticket and include the following text:

Wed Jan 11 2012 10:05:57 GMT-0500 (Eastern Standard Time)

The action involved likely succeeded, however, this part of the software needs to be updated to better understand success messages from the server, so please let us know about it.

{
"stacktrace":"/usr/local/share/perl/5.10.1/OpenILS/Application/Actor.pm:3167 /usr/local/share/perl/5.10.1/OpenSRF/Application.pm:564 /usr/share/perl5/Error.pm:416",
"ilsevent":"",
"pid":"12196",
"desc":"",
"payload":
[
"1301756"
]
,
"textcode":"MERGED_USER_IN_COLLECTIONS",
"servertime":"Wed Jan 11 10:05:49 2012"

We should get this event mapped in ils_events.xml in order to present a simple error message, rather than the scary looking debugging info.

Changed in evergreen:
status: New → Confirmed
Ben Shum (bshum) wrote :

Confirmed to occur in 2.2 series of Evergreen as well.

Galen Charlton (gmc) wrote :

Still in master. Marking bitesize.

tags: added: bitesize
Jeff Godin (jgodin) on 2013-05-31
tags: added: collections
Alex Lazar (alex-lazar) wrote :

Is it the intended behavior of Evergreen to not allow merging patron records if one of them is in collections status? In that case, would a friendlier message be something like "Patron records in collection status cannot be merged"?

Changed in evergreen:
assignee: nobody → Michael Peters (mrpeters)
Changed in evergreen:
assignee: Michael Peters (mrpeters) → nobody
Changed in evergreen:
assignee: nobody → Michael Peters (mrpeters)
Terran McCanna (tmccanna) wrote :

Marking this Won't Fix since the error messaging in the web client is different than it was in XUL. (However, there are still improvements that could be made to many of the web client error messages as well.)

Changed in evergreen:
assignee: Michael Peters (mrpeters) → nobody
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers