Scripturizer in PHP

<pre>John 3:16</pre>

30 thoughts on “Scripturizer in PHP”

1. Glen,

   Great! Well done. Actu­al­ly, I have also recent­ly dis­cov­ered NET bible and have been using it as a ref­er­ence to pre­pare for stud­ies. Can’t get rid of ESV because the church here uses it 🙂

   Per­form­ing the fil­ter­ing at publish/edit time is real­ly a great idea in reduc­ing CPU load, as I have been think­ing ways to speed up lay­ers and lay­ers of Word­Press con­tent fil­ter plu­g­ins. Got a 5‑year-old 400Mhz box serv­ing my site, which would take 1+ sec­ond to gen­er­ate the index page 🙁

   In Christ,

2. Awe­some. Will you post here (or com­ment here, then I’ll get noti­fied by my RSS read­er) when this merging/sourceforge thing hap­pens?
   *smiles sweet­ly*

3. I’ve found a “fea­ture”: Scrip­tur­iz­er does­n’t work (noth­ing hap­pens) if there are any lit­er­al apos­tro­phes any­where in the post. As a workround, you can use ' to include apos­tro­phes.

4. I’ve found a “fea­ture” — scrip­tur­iz­er does­n’t work (noth­ing hap­pens) if there are any lit­er­al apos­tro­phes (ASCII 39) any­where in the post!

5. Thanks for let­ting me know–I’ll try to get on that ASAP!

6. Can’t get it to work. Copied the code etc. uploaded the php file, acti­vat­ed it, all as spec­i­fied.
   But when I type a ref­er­ence it remains com­plete­ly un-scrip­tur­ized… can’t work out why. I must have done some­thing wrong…but it’s weird…

7. It seems that if the scrip­ture ref­er­ence is on a line by itself, it works fine, but some­times if it is in the mid­dle of a sen­tence, it does­n’t come though.

8. Thanks for pro­vid­ing this resource — and I need your help. I am try­ing to install this plu­g­in into my new site, but I keep get­ting a “call to unde­fined” error around line 52. Not know­ing any­thing about PHP, I can’t fig­ure out what the prob­lem is. Would you have any idea?

   Thanks,
   Pas­tor Hal Atkins

9. I’ve tried to repli­cate the bugs peo­ple have describes but have been unable to do so. Specif­i­cal­ly, I can’t repli­cate a sce­nario where Scrip­tur­iz­er fails with a sin­gle ’ nor where it fails in the midst of a sen­tence (and I can’t fig­ure out what’s wrong near line 52). If any­one can point me to a URL that fails it would real­ly help me debug this thing.

   Also, I haven’t heard from Dean or Scott in a while about merg­ing our code­bas­es. I assume they got busy, so I’ll con­tact them again…

10. Awe­some plu­g­in. The apos­tro­phe thing is a prob­lem, though, and the fix above (using ') does­n’t work. You have to use ' for all apos­tro­phes.

11. I installed the plu­g­in and acti­vat­ed it. Then went to write and got the fol­low­ing error

    Parse error: parse error, unex­pect­ed T_STRING in …/wp-content/plugins/scripturizer.php on line 52

    Line 52 reads
     // we skip tags because some­thing like should not be messed with

    any ideas?

    bri­an

12. Thanks for doing this!

13. I’m get­ting a sim­i­lar error to Bri­an in #17 above, except in line 55. Line 55 reads:

    if (preg_match($split_regex,$value)) {

    Ideas?

14. I too get an error after acti­vat­ing. I get the fol­low­ing error:
    
Parse error: parse error, unexpected T_AS in /home2/brianath/public_html/wordpress/wp-content/plugins/scripturize.php on line 53

    For me, Line 53 is:
    
$anchor_regex = ‘’;

    And just in case it may be an error before that, the last few lines of code (48 to 57):
    DEFAULT_BIBLE_TRANSLATION’,‘NIV’);

    func­tion scrip­tur­ize ($text = ‘’,$bible = DEFAULT_BIBLE_TRANSLATION){
    // skip every­thing with­in a hyper­link, a

     block, a  block, or a tag
        // we skip tags because something like  should not be messed with
            $anchor_regex = ‘’;
        $pre_regex = ‘
    .*
    ’;
    
        $code_regex = ‘.*’;
    
            $tag_regex = ‘ (?:[^>s]*)(?:s[^>]*){0,1}>’; // $tag_regex=’ [^>]+>’;
    
            $split_regex = “/((?:$anchor_regex)|(?:$pre_regex)|(?:$code_regex)|(?:$tag_regex))/i”;
    
    
    

15. I see the prob­lem. The code in the text box has been run through Word­Press’ out­put fil­ter and the sin­gle quo­ta­tion mark has been turned into a fan­cy apos­tro­phe.

    The short-term solu­tion is to do a search and replace.

    The long-term solu­tion is for me to fix this…

16. I think I must be doing some­thing wrong, but when I upload the scripturize.php file to the plu­g­ins fold­er and then go to it thru the admin inter­face to acti­vate it, the whole code is there instead of an acti­vate link. I’ve tried this three dif­fer­ent times from 3 dif­fer­ent sources with the same result. All of my oth­er plu­g­ins have just dropped right in. Any idea of what I may be doing wrong or what may be caus­ing this?

    Peace,
    Paul

17. Hi, I’m get­ting the same prob­lem as #20 and #22. When I look at the file, the line with the prob­lem seems to be $anchor_regex = ‘’;

Has a solution to this been found?
Please send me an email, since I might forget to check back! Thanks.

18. Great script, but have you had a chance to review the apos­tro­phe prob­lem? It’s the only thing keep­ing the script from being effec­tive.

19. The apos­tro­phe bug is gone now. What an awe­some script! Thanks Glen!

Comments are closed.