Summary: | Authorised value's descriptions should not be NULL | ||
---|---|---|---|
Product: | Koha | Reporter: | Jonathan Druart <jonathan.druart> |
Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
Status: | In Discussion --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | dcook |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 34920 | ||
Bug Blocks: |
Description
Jonathan Druart
2024-02-29 14:58:47 UTC
Katrin, could you confirm this assumption? In the past it was sometimes necessary to add an empty entry manually, as the pull downs would not offer one otherwise. So such entries might exist in the existing databases for a reason. I am not sure if they are still needed. How would a fix with the atomicupdate look like? Would we aim for deleting such entries? I believe just removing them could cause issues: a pull down that does not offer an empty entry on its own, would jump to the first entry in list, which would result in saving/displaying wrong values in forms. |