It seems that PatronSelfModificationBorrowerUnwantedField and PatronSelfRegistrationBorrowerMandatoryField are in conflict. There are certain pieces of information you may want when registering that you don't want a patron to modify online. For example, you will ask for the patron name when registering, but don't necessarily want them changing their names freely. Our library requires that they show an ID when they pick up their card after registration. If they legally change their name, they need to come in with an ID again to verify the change. I would suggest allowing the PatronSelfModificationBorrowerUnwantedField to have priority over the PatronSelfRegistrationBorrowerMandatoryField settings. So, if a field is listed in PatronSelfModificationBorrowerUnwantedField, it should negate the same field listed in PatronSelfRegistrationBorrowerMandatoryField. If not that, then there should be a separate field for mandatory modification fields called PatronSelfModificationBorrowerMandatoryField.
How is this is a major bug?
(In reply to Katrin Fischer from comment #1) > How is this is a major bug? Who says it is major? :)
I'd even say it's an enhancement. The changes are moderated - people are not able to change fields and it works like it always did - no regressions?
Potatoes/Tomatoes....I'll let you make that call. I think it is a bug because you can set it to not show and it still shows.
I wish the pref names were shorter :) After reading again I get your point.
*** This bug has been marked as a duplicate of bug 13188 ***