Browser requests to getbible.net fail now due to CORS issue #9
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: getBible/support#9
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi @Llewellyn,
There seems to be have been a recent change in the server settings of getbible.net. Requests like
await fetch('https://getbible.net/v2/checksum.json')
now fail when executed from other origins. This has broken the preview of my Bible reference tagger blinx.js, as can be seen on this page.Would you have time to look into this?
Thanks!
I am looking at this now... not sure why, as it worked.
Hmmm I see this issue. Our domain has changed:
https://api.getbible.net/v2/checksum.json
is the new path to the API.Let me know if this resolves your issue. You will see that getBible.net has been completely build over, and has a whole new application, that is by far more powerful than the one we had before.
I mean look at: https://getbible.net/kjv/Revelation/3/5
Our new application (Joomla Extension) has URL and search, with tags, and OpenAI abilities.
More info on the API and what we are doing go to: https://getbible.net/docs
Thanks for the quick response, @Llewellyn! Adjusting the domain does the trick!
How can I find out more about the upcoming "GROUPED VERSE SELECTION" feature?
That is still under development, I am trying to move that out into a lone standing application, and not make it directly part of the Joomla application as before.
I have been looking at a number of ways to achieve this, and have not yet made up my mind.
I had to move the due date to 1st of December 2023 because of this, yet I am really working hard to get it done sooner.
Do you know JQ? Using the existing API files, I was think of using JQ to serve the Grouped Verse Selection, which would mean chaining a number of technologies. I have not yet come to a final position on this, yet what I hope to achieve is a much faster, stable and long term solution that stand independent from Joomla.
What would you use if you had to build this based of the existing API json files?
Here is a playground for jq: https://jqplay.org/
The new QUERY-API for verse queries are located at:
The design allows for one translation at a time:
But with multiple scripture references:
The book name (or number) must be in each reference.
Please also note that the Result of the return set has changed, and is now more aligned with version 2 format.
Result:
Result:
Please use the default API for chapter calls, as this API is really only for verse queries, thanks!