Bug 35858 - Local cover image doesn't display on initial load of OpacBrowseResults
Summary: Local cover image doesn't display on initial load of OpacBrowseResults
Status: RESOLVED DUPLICATE of bug 31207
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-22 16:38 UTC by Lucas Gass (lukeg)
Modified: 2024-01-23 15:44 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Gass (lukeg) 2024-01-22 16:38:53 UTC
To recreate;

1. Enable OpacBrowseResults and OPACLocalCoverImages.
2. Add a local cover image for a record. 
3. Go to the OPAC detail page for that record and in the holdings table click 'Browse shelf'.
4. Notice the local cover image does not appear initially. 
5. Use the shelf browsers Previous/Next buttons to page away from the current record and page back.
6. When you get back to your record after Previous/Next'ing away you will see the local cover image.
Comment 1 Andreas Roussos 2024-01-23 10:38:52 UTC
Hi Lucas, I see you mentioned OpacBrowseResults in the Bug title and also
in the steps to recreate. Can I just confirm with you that it's necessary
for OpacBrowseResults to be enabled for this particular bug to manifest?

I'm asking because the description for the OpacBrowseResults System
preference is "Disable|Enable browsing and paging search results from
the OPAC detail page." i.e. at first glance it seems unrelated to the
OPAC Shelf browser.

Perhaps you meant "Enable OPACShelfBrowser and OPACLocalCoverImages."
in step 1? Just a guess...

If so, that would make this Bug report a duplicate of Bug 31207, I think.
Comment 2 Lucas Gass (lukeg) 2024-01-23 15:44:34 UTC

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