Bug 30083 - Bug fixes 29914 and 28785 make 'Browse result' feature disappear for anonymous user
Summary: Bug fixes 29914 and 28785 make 'Browse result' feature disappear for anonymou...
Status: RESOLVED DUPLICATE of bug 29915
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: 21.05
Hardware: All All
: P3 normal (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2022-02-11 16:06 UTC by Janusz Kaczmarek
Modified: 2023-06-17 14:08 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Browse results (26.36 KB, image/png)
2022-02-11 16:06 UTC, Janusz Kaczmarek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Janusz Kaczmarek 2022-02-11 16:06:47 UTC
Created attachment 130512 [details]
Browse results

In OPAC, having OpacBrowseResults on, a Browse results widget should be available, with a very helpful feature of moving to the next / previous record (cf. the graphics attached).

However, in version 21.05.10 the bug fix 29914, and in version 21.11 both the bug fixes 29914 and 28785 (changes to C4/Auth.pm) make the widget not appear for an anonymous (not logged in) user.  Which is pity and annoying. 

As far as I was able to investigate, this is because a session information is not being maintained for an anonymous user and so the 'busc' parameter is not passed to the opac-detail.pl script.

Reverting the bug fixes makes the widget reappear.  Obviously, this is not a solution.  Nevertheless, it reveals the cause.
Comment 1 Janusz Kaczmarek 2022-02-11 16:53:41 UTC
To be precise: Browse results widget should be available on the OPAC detail page.
Comment 2 Lucy Vaux-Harvey 2022-02-11 17:43:54 UTC
Thanks for logging this bug, we are seeing the same issue on the OPAC at 21.11 for users who are not logged in.
Comment 3 Jonathan Druart 2022-02-15 09:38:27 UTC
This problem will be fixed by bug 29915. However it's not a trivial change and I don't know if we should backport it.
Comment 4 Katrin Fischer 2023-06-17 14:08:04 UTC

*** This bug has been marked as a duplicate of bug 29915 ***