https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30691
Phil Ringnalda <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |ASSIGNED Depends on| |21958 CC| |[email protected], | |[email protected] Severity|enhancement |normal --- Comment #3 from Phil Ringnalda <[email protected]> --- Test plan can't go in that order, because GuessAuthTypeCode runs and we throw when you save the authority record. So it has to be * Leave SearchEngine set to Zebra * Edit MEETI_NAME framework, uncheck Mandatory for tag 111 * Create authority with 147 and no 111 * Switch SearchEngine to ElasticSearch, reindex Seems like a bug that we include 147 in every authtype framework, since having two 1xx headings in an authority record is both invalid and not going to work, and you have to go to a lot of trouble to make the one that should be mandatory for that authtype not mandatory to have the 147 even pretend to do something. But since 147 and 162 exist, but are too obscure to be worth shipping an authtype framework for them, this seems like a reasonable solution if people do the wrong thing trying to use them. The patch doesn't work, though, since some stray whitespace crept into "->as _string." Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21958 [Bug 21958] _check_valid_auth_link checks too many subfields -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
