OPAC Hold edits no longer save

Bug #1865533 reported by Terran McCanna
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned

Bug Description

In Evergreen 3.4.2:

If a patron suspends a hold and then goes into their holds list to edit it through the OPAC, they can select a hold activation date, change status between suspended/activated, change notification preferences, etc. but none of the changes actually save. (The Actions drop down still works to suspend/activate, but not the Edit options.)

To recreate:

1. Log into the OPAC.
2. Place a hold.
3. Go to My Account > Holds > Items On Hold
4. Click the Edit link next to the hold you placed and edit the pickup location, active/suspended status, notification method, etc. and Submit.
5. Return to My Account > Holds > Items On Hold to see that none of the changes were saved.

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

I think this was also noted by Dawn Dale in comment 8 of bug #1783793 for evergreen 3.4.1.

Josh

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

I tested our 3.3.4 system and the opac hold edit button features seem to work fine in that version.
Josh

Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Tested this in 3.5 beta and I can confirm that changes made in the Edit screen under Items on Hold in the OPAC don't save.

I've tried suspending with an activation date, adding a Cancel unless filled by date, and changing the Phone Notification number.

Clicking Submit takes me back to the Items on Hold screen without displaying an error but my change is not saved.

Changed in evergreen:
status: New → Confirmed
Changed in evergreen:
importance: Undecided → Medium
milestone: none → 3.5.0
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

A blank "SMS Notification" field is being treated as an empty string ("") rather than a null value, which causes the hold update to fail. Working branch user/jeffdavis/lp1865533-edit-hold-save-changes has a fix:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jeffdavis/lp1865533-edit-hold-save-changes

tags: added: pullrequest
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

This fix works for me on our 3.5beta test server. I'm leaving it to someone else to test and signoff though (since I'm at the same org at Jeff).

Revision history for this message
Terran McCanna (tmccanna) wrote :
tags: added: signedoff
Revision history for this message
Chris Sharp (chrissharp123) wrote :

Pushed to master and 3.5 - thanks Jeff, Jennifer, and Terran!

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
Revision history for this message
Galen Charlton (gmc) wrote :

Noting for anybody who was confused, like me, that this wasn't a bug in stock 3.4.x, but was an problem in 3.5-beta; the regression was due to the original patches for bug 1570072.

no longer affects: evergreen/3.4
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.