If you add branchcode to PatronSelfRegistrationBorrowerUnwantedField then self registration fails silently. The library and the user have no idea what happened. We should have an error and/or not let branchcode be added to that preference.
-- or add a default branch code? :) Similar to bug 16892 that I did for the OAuth2 auto-register.
This is not critical, it's a configuration issue.
The problem is that when hiding the branchcode, which is desirable for singel branch libraries, the email disappears. And without the email the verification process breaks. Normal is ok, becuase you can have work around it, but would be nice to see fixed. I see no reason why there should be any link between hiding email and branch. Also: altcontactnote can't be hidden... haven't investigated deeper yet.
Katrin, I do not understand. Which email are you talking about?
The primary email field in the form where you enter the patron data.
Sorry for all the typos in my previous comment. The system preference *unwanted* takes the database column names from the borrowers table. When you enter 'branchcode' it will hide more fields, especially the primary email (email) field, which doesn't make sense.
I do not recreate, I have added "branchcode" to PatronSelfRegistrationBorrowerUnwantedField, when I go to opac-memberentry.pl I do not see the library entry and see "primary email" in the "contact information" part.
It's odd, I was testing in a 16.11.12. Will try to retest on master soon.
I retested this on master and couldn't replicate the 'disappearing email', but found another explosion: Broken FK constraint at /usr/share/perl5/Exception/Class/Base.pm line 88 PatronSelfRegistrationBorrowerUnwantedField: branchcode PatronSelfRegistrationLibraryList: CPL (same with empty) Maybe we should catch the error and at the same time add a note to the pref that branchcode should not be hidden? Not sure how we determine the branch for the patron if it is hidden. Maybe we could hide it, if there is only one entry (no more libraries configured, *LibraryList only has one entry)
*** Bug 26568 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 17364 ***