Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
As I stated in another comment I actually wonder if it isn't time for a complete rewrite in light of the eBible API which would enable us to do some of the nice things I showed in my patched version that we are able to do for the ESV for a much wider range of translations (and I suspect for less work)...
I'm not sure if Steve is still about as he hasn't committed any changes in 9 months, although he did respond to an issue last December...
We could at this stage I suspect hack together a Drupal 6 compliant module but really the code has grown over the years and is now no longer really using the best APIs available to us, so I would like to see a fresh Drupal 6 version from the ground up.
Yes, I just released a version for 6.0, which should show up in the release list shortly.
We could at this stage I suspect hack together a Drupal 6 compliant module but really the code has grown over the years and is now no longer really using the best APIs available to us, so I would like to see a fresh Drupal 6 version from the ground up.
Assuming I updated the module correctly, migrating it from v5 to v6 just involved one simple change. As far as updating the code, I'm all for anything that will make the module simpler and easier to maintain (and there's definitely room for improvement there), but I'm not all that interested in changes that will make it more complex and/or error-prone. That's probably the realm for a new module.
Comments
Comment #1
andykemp commentedAs I stated in another comment I actually wonder if it isn't time for a complete rewrite in light of the eBible API which would enable us to do some of the nice things I showed in my patched version that we are able to do for the ESV for a much wider range of translations (and I suspect for less work)...
I'm not sure if Steve is still about as he hasn't committed any changes in 9 months, although he did respond to an issue last December...
We could at this stage I suspect hack together a Drupal 6 compliant module but really the code has grown over the years and is now no longer really using the best APIs available to us, so I would like to see a fresh Drupal 6 version from the ground up.
Comment #2
tcblack commentedsubscribing
Comment #3
Steve Simms commentedYes, I just released a version for 6.0, which should show up in the release list shortly.
Assuming I updated the module correctly, migrating it from v5 to v6 just involved one simple change. As far as updating the code, I'm all for anything that will make the module simpler and easier to maintain (and there's definitely room for improvement there), but I'm not all that interested in changes that will make it more complex and/or error-prone. That's probably the realm for a new module.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.