| Summary: | Custom authorized values do not appear in a selector in Advanced Editor | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Esther Melander <esther.melander> |
| Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED WORKSFORME | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | m.de.rooy, phil |
| Version: | unspecified | ||
| 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
Esther Melander
2024-08-21 19:22:31 UTC
As long as I do the steps in that order, and modify step 1 to say "Add some values *and descriptions* like..." since otherwise the advanced editor will show the options as "null", it works for me. The order of steps that doesn't work, since the advanced editor loads authorized values as a part of loading the framework, would be 1. Open the advanced editor with the default initial load of the Default framework 2. Create an AV 3. Edit the framework to use the AV 4. Add 100 _ _ ‡e to the open editor Or an alternate step that fails, "Create an authorized value category, then create two values: for one, fill in the value and the description, for the other, fill in the description and the description (opac) but fail to fill in the value" because that will make the advanced editor refuse to show a dropdown. Could you both check your exact Koha version please? Maybe this will give us a lead. 24.06.00.023 for me, not sure if I pulled before or after testing this last night, and it doesn't help that the timestamp on my comment is clearly wrong by several hours. (In reply to Phil Ringnalda from comment #3) > 24.06.00.023 for me, not sure if I pulled before or after testing this last > night, and it doesn't help that the timestamp on my comment is clearly wrong > by several hours. Ok, but you were testing on main then. That's good to know. I believe we fixed a bug in this area, but didn't find it right away. Trying to limit things down a bit. Esther, where did you see this? I initially found it in 24.05.02. In my testing today, I am not able to reproduce. Would indexing be a factor? It is odd that it wasn't working and is now. I would be fine with marking the ticket as invalid since it can't be predictably reproduced. OK, let's close, but please re-open if this re-appears! |