| Summary: | Hide 856$y when $u is missing | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Esther Melander <esther.melander> |
| Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | m.de.rooy |
| 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-02-16 20:18:59 UTC
Hi Esther, have you hidden $y in the OPAC as well? I believe $u was removed, but the link was still built with $y as the text - that would explain why the link broke. If $u is hidden, should $y appear in the OPAC as a clickable link (especially if the URL box is unchecked)? The link will be broken and return an error page, but should it even appear in the first place? I would think that if $u is hidden, $y should either be hidden automatically as well or only appear as text. (In reply to Esther Melander from comment #2) > If $u is hidden, should $y appear in the OPAC as a clickable link > (especially if the URL box is unchecked)? The link will be broken and return > an error page, but should it even appear in the first place? I would think > that if $u is hidden, $y should either be hidden automatically as well or > only appear as text. We could make it more clever like that, but I think that makes it a different kind of bug. The problem is that the logic in our XSLT could be smarter, but the visibility settings work as expected. $u is hidden when set to hidden, $y is kept. there are no relationships/dependencies between the subfields in the frameworks. I am changing the bug description a little bit to reflect that. |