tpac: default notifications not displaying in My Account

Bug #999218 reported by Kathy Lussier
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Low
Unassigned

Bug Description

Evergreen version: 2.2 RC1

Thanks to https://bugs.launchpad.net/evergreen/+bug/980988, if a user does not have a usr_setting entry for opac.hold_notify, the default options for notify by phone / email are now selected when placing a hold. These options are also selected by default in the patron record editor. However, they are not selected by default in Notification Preferences for "My Account."

Changed in evergreen:
status: New → Triaged
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Evergreen 2.8.1

It appears that when a new patron is registered the default hold notification settings (for whichever options are selected) are not actually created which is why they are not displaying in "My Account".

The work around is to open the patron's account, unselect all default notifications, save the patron's record, re-select the desired default notifications, and save the patron's record. The setting are then created in the database. Having the patron select default notifications via "My Account" also saves these settings properly.

Revision history for this message
Kathy Lussier (klussier) wrote :

This is partially fixed in webby. In the web client patron editor, the pre-selected home and email options are submitted as notification preferences and stored in the actor.use_settings table. As a result, the two options are selected when the new user retrieves the Notification Preferences tab.

However, the phone number to be used for phone notifications does not automatically populate the phone number field in My Account as it does on the Place Hold page.

Revision history for this message
Terran McCanna (tmccanna) wrote :

Confirmed that behavior is still as described in Kathy's 2017 message in 3.2.3. Changing title to reflect change in behavior from original message.

tags: added: holds myaccount opac
removed: tpac
Changed in evergreen:
status: Triaged → Confirmed
importance: Undecided → Low
Revision history for this message
Terran McCanna (tmccanna) wrote :

I am no longer seeing an issue with this as of 3.6 with the AngularJS patron registration form and the Bootstrap OPAC.

Changed in evergreen:
status: Confirmed → Won't Fix
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.