Ebook API: OverDrive download link non-functional in My Account

Bug #1677813 reported by Jeff Davis
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

Evergreen 2.12

With OverDrive ebook API integration enabled, a user's current OverDrive checkouts are displayed under the "E-Items Checked Out" tab in My Account. However, the Download link does not work. Additionally, holds that are ready for checkout don't have a Download link. In 2.12, these should be links to the external OverDrive title details page.

(In EG 3.0, the Download link should be replaced with a button allowing direct download without leaving the OPAC.)

Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

Fix in branch user/jeffdavis/lp1677813-ebook-api-download-link in working repo. Needs testing.

Revision history for this message
Kathy Lussier (klussier) wrote :

Jeff,
Is this bug ready for a pullrequest?
Kathy

Revision history for this message
Kathy Lussier (klussier) wrote :

I decided to give the branch a whirl even without the pullrequest. I'm having trouble with the code. With the new code, when I log into my account, I no longer get the e-book dashboard in the upper right screen. The e-item tabs display in My Account, but my checked-out titles and titles on hold are not displaying.

I've verified that ebooks and Overdrive are enabled in config.tt2 and that these elements are displaying as expected when the new code is removed.

Changed in evergreen:
milestone: 2.12.1 → 2.12.2
Changed in evergreen:
milestone: 2.12.2 → 2.12.3
Changed in evergreen:
milestone: 2.12.3 → 2.12.4
Changed in evergreen:
milestone: 2.12.4 → 2.12.5
Changed in evergreen:
milestone: 2.12.5 → 2.12.6
Changed in evergreen:
milestone: 2.12.6 → 2.12.7
Changed in evergreen:
milestone: 2.12.7 → 2.12.8
Changed in evergreen:
milestone: 2.12.8 → 2.12.9
Changed in evergreen:
milestone: 2.12.9 → 2.12.10
Changed in evergreen:
milestone: 2.12.10 → 2.12.11
Revision history for this message
Kathy Lussier (klussier) wrote :

Because additional functionality was added in 3.0, this bug is specific to 2.12, which reaches end of life later this week. Setting this bug to Won't Fix.

Changed in evergreen:
status: New → Won't Fix
Changed in evergreen:
milestone: 2.12.11 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers