Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Pressing "Block details" button from Renewals is causing system crash

Description

Holly found this error while checking something else out on http://folio-q4-core.aws.indexdata.com. She was able to recreate the error several times on Sunday.

  1. To test this you need to first checkout an item to a patron and then enter a patron block for that same patron.

  2. Then go to the patron's open loans and do a renewal, which will be blocked (as shown in attached screen print Blocked-from-renewal.jpg).

  3. Press the Block details button to get more information about the block, which is what most users will do, and a system error occurs (as shown in attached screen print System-error.jpg).

Important note: When Holly presses the "Block details" button from Checkout and Requests she does NOT get this error. It only happens within Renewals.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Holly MistlebauerJune 11, 2019 at 9:50 PM

Holly MistlebauerMay 21, 2019 at 5:48 PM

Holly tried to test this today at https://folio-snapshot-stable.aws.indexdata.com, but Requests aren't working.

Holly MistlebauerApril 23, 2019 at 11:26 AM

Hi Zak. Thanks for the update. I was planning on reassigning this issue to the Core group, now I don't have to. I will test this out shortly.
Thanks again,
Holly

Zak BurkeApril 23, 2019 at 11:13 AM

, there were a few places in the ui-users codebase that contained the incorrect sort clause, Name, which have now been fixed. This resolves the JS alert you could generate from within the application. If you have a browser shortcut that points to ...sort=Name, there is not much I can do about it, and the fact that your browser auto-corrected ...sort=name to ...sort=Name is probably related to the latter being in your history.

That said, there are ongoing discussions about how the UI could/should protect against bad values from a URL making it into a query that causes an Okapi error.

Holly MistlebauerApril 3, 2019 at 2:55 PM
Edited

, regarding the error I reported above...

My browser shortcut goes to http://folio-snapshot.aws.indexdata.com/users/view/?sort=Name. I thought about what you said regarding Name vs. name and changed the URL I use to http://folio-snapshot.aws.indexdata.com, then selected Users and undergrads. The error no longer appears.

P.S. When I tried to use http://folio-snapshot.aws.indexdata.com/users/view/?sort=name it was automatically changed to http://folio-snapshot.aws.indexdata.com/users/view/?sort=Name when I hit enter.

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Development Team

UNAM

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 21, 2019 at 1:23 AM
Updated October 8, 2020 at 3:39 PM
Resolved June 11, 2019 at 9:50 PM
TestRail: Cases
TestRail: Runs