Library setting - require at least one patron address is not working as expected

Bug #1010596 reported by Shae
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Undecided
Unassigned

Bug Description

When the setting to require at least one patron address is set to False, the expectation is that on the patron registration screen, it would no longer show as required and you can save the record without filling anything in. Here is what's happening:

1. On the patron registration screen, it still LOOKS like the address info is required.
2. If I try to save the record without any info there, it tells me "form is invalid."
3. I have to click the X on the patron address to completely delete it before I can save the record.

This is true in 2.1 and 2.2 including the 2.2. rc1. Tested internally and on a customer site so not limited to one system. Thank you.

Revision history for this message
Ben Shum (bshum) wrote :

I think this was "public notes" under the unsponsored list of pending features for Tpac on the wiki. I've updated the page accordingly and linked to this bug ticket.

http://evergreen-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:plan

Marking ticket as confirmed, wishlist.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Wishlist
tags: added: tpac
Revision history for this message
Ben Shum (bshum) wrote :

Gah, ignore above, was posting on the wrong bug ticket entry :(

Changed in evergreen:
status: Confirmed → Triaged
importance: Wishlist → Undecided
Revision history for this message
Thomas Berezansky (tsbere) wrote :

On the subject of the actual ticket in question...

I think this is "working as expected" - At least for me. If you have an address those fields are required, and patron registration includes, as part of the defaults, an empty address.

About the only thing I can think of for changing the way the interface works would be to say "if you as an explicit action (setting is there, compared to unset) do not require an address then don't generate an empty one for patron registration". That would change the behavior to needing to add an address before you could populate it.

I do not think that the setting should change the required nature of the address fields when there is an address (empty or otherwise).

Ben Shum (bshum)
tags: removed: tpac
tags: added: circulation patron
Revision history for this message
Terran McCanna (tmccanna) wrote :

This is currently working as expected - I can change the setting to False, delete the address subform from a patron registration, and save with no problems.

Changed in evergreen:
status: Triaged → 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.