Bug 37145 - Koha ERM data provider name search broken
Summary: Koha ERM data provider name search broken
Status: RESOLVED DUPLICATE of bug 37043
Alias: None
Product: Koha
Classification: Unclassified
Component: ERM (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low normal
Assignee: Kyle M Hall (khall)
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-20 16:53 UTC by Kyle M Hall (khall)
Modified: 2024-06-21 13:19 UTC (History)
8 users (show)

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

Attachments
Bug 37145: Koha ERM data provider name search broken (1.24 KB, patch)
2024-06-20 16:57 UTC, Kyle M Hall (khall) 		Details | Diff | Splinter Review
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall (khall) 2024-06-20 16:53:42 UTC 
This is broken because the FQDN for the service has changed and we do not handle the 301 gracefully.

To test:
1) Browser to ERM / eUsage / Data roviders
2) Click "New data provider"
3) Start typing anything into "Data provider name"
4) Note the error: "Something went wrong: Error: Internal Server Error."
Comment 1 Kyle M Hall (khall) 2024-06-20 16:57:08 UTC 
Created attachment 167939 [details] [review]
Bug 37145: Koha ERM data provider name search broken

This is broken because the FQDN for the service has changed and we do not handle the 301 gracefully.

Test Plan:
1) Browser to ERM / eUsage / Data roviders
2) Click "New data provider"
3) Start typing anything into "Data provider name"
4) Note the error: "Something went wrong: Error: Internal Server Error."
5) Apply this patch
6) Restart all the things!
7) Repeat step 3
8) No error!
Comment 2 Chris Cormack 2024-06-20 22:53:35 UTC 
This was fixed by bug 37043 (which has been pushed to main already)
Comment 3 Kyle M Hall (khall) 2024-06-21 13:19:56 UTC 

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