| Summary: | Staff-only extended attributes break self-registration | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Jason Boyer <JBoyer> |
| Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | aude.charillon, caroline.cyr-la-rose, cbrannon, gmcharlt, kyle |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Jason Boyer
2023-07-17 14:09:44 UTC
Still valid in master (23.06.00.060)
To recreate:
0. PatronSelfRegistration is enabled by default, but if it's not on your system, turn it on
1. Create a mandatory patron attribute type
1.1. Go to Administration > Patron attribute types
1.2. Click New patron attribute type
1.3. Fill out the form as follows:
- Patron attribute type code: Enter a code (e.g. BZ34295)
- Description: Enter a description (e.g. Bug 34295)
- Mandatory: check
1.4. Click Save
2. Try to register online
2.1. Go to the OPAC (log out if necessary)
2.2. Click Register here
2.3. Fill out the form
--> The attribute should not be visible
2.4. Click Submit
--> Error
(In reply to Aude Charillon from comment #2) > Is this the same situation as in bug 38005? No. That bug is specific to a conflict with the OPAC itself. I am running into this issue with Aspen self registration. The staff mandatory seems to be affecting the self registration API, which Aspen uses. But Aspen is doing this on behalf of the patron. It seems like their should be a self registration API that adheres to the OPAC rules. |