Glen Davis

UPDATE 12/23/2004: I’ve moved my ver­sion of the code to the new WP Plu­g­ins repos­i­to­ry, so you can down­load it at http://dev.wp-plugins.org/file/scripturizer/trunk/scripturizer.php

UPDATE: plans are afoot to merge the three exist­ing code­bas­es (Dean’s, Scott Yang’s, and this one) into a sin­gle Source­forge project. (UPDATE 12/23/2004: noth­ing has real­ly come of that–we’re all a lit­tle busy and haven’t real­ly worked to make it hap­pen. Oh well…)

---

Not real­iz­ing that Mean Dean was port­ing Scrip­tur­iz­er to PHP, I went ahead and did it so that I could begin using it on this Word­Press site. At about the same time Scott Yang made one, so there are two ver­sions out there. Sor­ry about that.

I orig­i­nal­ly was­n’t going to pack­age it for release, but it turns out that I had to do it to actu­al­ly use it on my site :), and so I fig­ured I might as well put it in the pub­lic ver­sion to make it easy for any­one else to use. Also, fig­ur­ing out how to use add_action was nonob­vi­ous (at least when I first did this–I believe the doc­u­men­ta­tion has improved con­sid­er­ably), so I want­ed to pro­vide a clear exam­ple.

It extends the func­tion­al­i­ty of the orig­i­nal and also changes the data per­ma­nent­ly in the user’s data­base (as opposed to Scot­t’s, which fil­ters it on the fly). You can set mine to do that (see the source code), but Scot­t’s will work that way out of the box. Which you pre­fer is up to you. Mine is more effi­cient, his affects all the archives with­out mak­ing you man­u­al­ly edit any­thing.

Usage: just copy the source code to a file named scripturize.php in your wp-con­tent/­plu­g­ins fold­er. Go to your admin­is­tra­tion pan­el, click on Plu­g­ins, and acti­vate it. Then just refer to the Bible in your posts. If you don’t want a Bible ref­er­ence hyper­linked, be sure to enclose it in pre­for­mat­ting tags, like so:

<pre>John 3:16</pre>

Changes from Dean’s orig­i­nal:

• You can spec­i­fy a trans­la­tion you want to link to by putting the stan­dard abbre­vi­a­tion after the ref­er­ence like so: John 3:16, NIV or 2 Cor 5:20 (NET). This one is huge, for me.
• Added New Eng­lish Trans­la­tion. I like this trans­la­tion for sev­er­al rea­sons, but most­ly for its philo­soph­i­cal under­pin­nings.
• Made syn­tax a lit­tle more per­mis­sive. For instance, you can now spec­i­fy a ref­er­ence by say­ing Gen. 12:1 or Gen 12:1 (period/no peri­od).
• Made syn­tax a lit­tle less per­mis­sive as regards white­space. Just write things nor­mal­ly and every­thing will work fine (I changed this to cor­rect some errors I was see­ing where­in the link would run into the blank space after the ref­er­ence).
• The reg­u­lar expres­sions han­dle link­ing a lit­tle bit dif­fer­ent­ly. It does some­thing more use­ful when con­front­ed with a crazy ref­er­ence like Rom 1:3, 5–8, 10,12 that the online Bibles don’t know what to do with.
• As I men­tioned, by default it will actu­al­ly change your post as stored in your data­base. For­ev­er. Irre­versibly. With no back­up. Just be aware of that.
• You can now spec­i­fy a default trans­la­tion. It is ini­tial­ly set to the NIV, because I assume that’s what most peo­ple will want.

Please Report Bugs In Bug Track­er
I’d real­ly like to know if you catch any bugs. I use this plu­g­in myself, so bugs direct­ly affect me! 🙂

There is a bug track­er set up at http://dev.wp-plugins.org/newticket, so please report any prob­lems there.