combine two tables in TPAC patron notification preferences page

Bug #1613381 reported by Galen Charlton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Wishlist
Unassigned

Bug Description

The TPAC My Account notification preferences page currently defines two tables:

- various hardcoded options for hold and SMS notifications
- preferences coming from opt-in settings for Action/Trigger event definitions

The two tables have slightly different styles, which can look odd, but they also don't express a distinction that patrons necessarily care about: i.e., I as a patron may want to tweak which notifications I get from the library, but I don't particularly care whether that preference arises from an opt-in setting or from a static YAOUS.

I propose to merge the two tables into a single table.

Evergreen master

Revision history for this message
Galen Charlton (gmc) wrote :

A patch is available in the user/gmcharlt/lp1613381_combine_patron_notification_prefs_tables branch of the working repository:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1613381_combine_patron_notification_prefs_tables

tags: added: pullrequest
Revision history for this message
Mike Rylander (mrylander) wrote :

It's in master! Thanks, Galen.

Changed in evergreen:
status: New → Fix Committed
Changed in evergreen:
milestone: none → 2.11-beta
status: Fix Committed → Fix Released
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.