The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I've had requests from my clients to use biblegateway for everything. At the moment this module automatically uses ESV online Bible for the ESV bible.
Why is this and what do you think about the option to allow you to select the bible site to use?
Chris
Comments
Comment #1
jamesoakleyHi Chris
That's a reasonable enough request.
Why does the site use the ESV online Bible site for the ESV? Because I inherited the module that way from the previous maintainer.
Do you have any suggestions as to how the site should present the option to use Bible Gateway for everything? Options I can think of are: (i) force it on everyone regardless; (ii) present it as an option so that you can choose "Bible Gateway for Everything" if you wish; (iii) create extra abbreviations for names of translations - say, ESVBG, for "ESV on Bible Gateway".
Thoughts?
Comment #2
chunty commentedWell.......hmmm.....(pauses and stare's at screen)....
I don't think option 1 is really an option since some people will already be using the module and might like how it works now. Option 2 is the easiest but not most flexible.
I like option 3 but its probably a bit techy for general users
I guess it depends if you want to support more vendors in the future (personally I really like the YouVersion site)
So to have a solution that was techy for admin/developers but not users we could do something like:
# Have a list of vendors (right now there are three)
# Have a table of versions
# Have mapping table in the db storing which bibles are supported by which vendors (I wouldn't expect this be admin-able really)
# Then provide an interface to allow admins/developers to map versions (e.g. ESV) to vendors
but perhaps combine this with your option 2 as an "Advanced" config or something. This would fix it for me and most other thats perhaps just want a single system but also also people to override a per version level whilst still allowing their users to use the standard references.
Thanks so much for responding so promptly
Chris
Comment #3
jamesoakleyThanks Chris
Your suggestion makes a lot of sense.
It relates to #149898: Updating Scripture Filter to load verse text into the page itself, because if that were ever implemented there would be some Bible versions that are not available through any API, so there would need to be a way to specify what to do in that case.
This is a bigger job - I won't get round to it in a hurry, and it will probably be Drupal 7 only. However if someone wants to contribute some code to start it moving, that obviously helps things move faster!
Comment #4
jamesoakleyPostponing this issue.
This is a feature request. The highest priority feature for Scripture Filter is preparing a Drupal 8 version. Once a Drupal 8 version is ready, I can then turn my attention to working on improvements. Those would be developed for Drupal 8 first, and then backported.
Comment #5
jamesoakley