Bibliasoft -- BibleFilter 1.2

[UltraVR]

This hack is outdated. Please visit here for version 1.5 (https://vborg.vbsupport.ru/showthread.php?t=127332)

Note: versions 1.5 and above should still be compatible with vBulletin 3.5.x

[UltraVR]

-Reserved-

[UltraVR]

-reserved-

[Holidazed]

So why the new mod? What is the difference between this and the one you have at https://vborg.vbsupport.ru/showthread.php?threadid=107513 (which you stopped supporting)?

[UltraVR]

I only stopped supporting the old one about 3 minutes ago when I released this one (because of its shiny newness), haha.

This one has a bunch of new features, a new product name, and I have laid the foundations for my plans for new features. Also, it is being released as the first product of Bibliasoft (which I hope will release a bunch of other stuff too).

[Holidazed]

Cool. I will uninstall the old one then and install this one instead. Thank you

[UltraVR]

You are very welcome.

[jpt62089]

Awesome! You should add support for [AJAX] vBShout v2.0 (https://vborg.vbsupport.ru/showthread.php?t=93097)

[UltraVR]

If you would like to add support to most any page or thing within vbulletin, simply surround the variable or text to be parsed with scripturize().

For example,

scripturize($post);

or

scripturize("John 2:12 is my favorite verse");

I'm sure this could be easily done in vbShout

[Murty]

Nice work man :D, will install tomorrow probly

[Tee]

This is perfect for my site!

[user02934123123]

Well done on the new version, which makes some of the settings easier to configure, and adds convenient support for various translations and an option of verse/chapter separaters (colon and full stop).

To port over from the previous hack's thread, here are my comments on features that would be desireable in the next release:

Thanks for this excellent product. I've installed it on our site, and the members are extremely pleased with it.

I'd like advice on increasing its functionality somewhat, along the following lines:

1. Is it possible to configure the hack so that it recognises the full stop (.) as well as the colon (:) as a chapter-and-verse separator (thus John 1.14)? This is the more common separator in some countries, and indeed in most academic theological writing (on which our forum focuses).

This has now been dealt with in the new release; many thanks.

2. The books of the 'Apocrypha' (Tobit, Sirach, etc.) are very important for much historical study of Christian history, and are supported on biblegateway.com, which provides the scripture engine behind this hack. However, I don't see that the hack itself supports these books. How could these be added in to its functionality?

This issue still remains. I would consider it the most pressing matter for the next release, since use of the hack on fora that deal with scriptural history, early Christianity, etc., require access to these books, and the lack of the hack supporting them severely limits its overall value.

3. Is it possible for the hack to provide support for alternative transliterations of book names? Many Eastern Orthodox people know and refer to book names as they exist in English through Greek rather than Hebrew sources -- thus Isaias rather than Isaiah, Avakoum rather than Habbakuk, etc. Could this hack be configured in some way to support both variants on such names?


This one is less urgent than the above, but should be fairly easy to code, so perhaps could also make it into a soon-in-coming new release. I am happy to provide a listing of the alternative spellings / titles for books.

[UltraVR]

I am working on the Apocrypha support for the next release, as it isn't difficult to include the names and abbreviations for them in the regular expression. There may be an issue with certain translations, but I'll play with Bible Gateway and see what I can work out.

A list for option 3 with corresponding names would make the process faster for me, but that option will probably be pretty time consuming to the code, and require a lot of new conditionals.

[user02934123123]

It would also be nice if this hack could be modified so that scripturizing takes place in the preview screen, so users see the linked references in the preview and can make changes if need be. So far as I can tell, the hack currently only applies the linking when the post is actually submitted to the system, but not in the preview pane -- something I know has confused two or three of my members.

Is there a way to wrap the scripturizing code around the preview template somehow?

[Pamela]

*clicks install*

Works perfect! Love it!!!

Thank you!!! :banana: