---- Reported by firstname.lastname@example.org 2010-01-06 19:37:19 ----
It would be useful to have the ability to make patron attribute types mandatory.
---- Additional Comments From email@example.com 2010-03-02 14:00:05 ----
Created an attachment
This patch adds the ability to make a patron attribute type mandatory.
--- Bug imported by firstname.lastname@example.org 2010-05-21 01:22 UTC ---
This bug was previously known as _bug_ 4030 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4030
Imported an attachment (id=1790)
Actual time not defined. Setting to 0.0
Setting qa contact to the default for this product.
This bug either had no qa contact or an invalid one.
The original submitter of attachment 1790 [details] [review] is unknown.
Reassigning to the person who moved it here: email@example.com.
Needs a new patch, this contains HTML::Template::Pro templates
This looks like it would be useful to pick up again. Is there a problem with it besides the template issue?
*** Bug 4418 has been marked as a duplicate of this bug. ***
*** Bug 20288 has been marked as a duplicate of this bug. ***
I looked at the patch, I think it's a lot more complicated than it needs to be. Right now, Each of the borrower attribute select statements generated by memberentrygen.tt looks like this:
<select id="patron_attr_1" name="patron_attr_1" class="noEnterSubmit">
The id for the second is patron_attr_2, etc.
If we change this to use values from borrower_attribute_types.category_code as the ID, I believe that we can then simply use these category codes in BorrowerMandatoryField.