1.6 Dev – Westminster Shorter Catechism August 30, 2006
Posted by LO in Development, Releases.trackback
I’ve been playing around with a new feature which allows users to reference the CCEL version of the Westminster Shorter Catechism, and I’d like to get some feedback.
If you are interested in trying out the new feature, download Scripturizer Dev 1.6 and use either of the following two reference formats in your posts:
- WSC 1; WSC 64; etc…
- Westminster Shorter Catechism 99
Let me know what you think . . . Like? Dislike? (O come on, I know there’s got to be some Presby bloggers out there! 
Also let me know if you find any bugs.
I just found this site. I love the scripturizer plugin, thank you for all your work. I would love to see an ability to cite the Westminster Shorter Catechism, one that might later be extended to other documents, i.e. The Augsburg Confession, Book(s) of Common Prayer, The Heidelberg Catechism, Articles of Religion etc…
I had a question also… I’ve been using scripturizer for several weeks now, and I really love it, especially the drop-down capability of the ESV version. I would like the ability to cite sections from the apocryphal books since they come up occasionally in our lectionary, or as optional readings in particular services. I have attempted to find a way to do this, but to no avail. Basically I would like to figure out how this site is doing what it is doing: http://www.scripturati.com/
unfortunately, the blog is no longer active… Just an idea…
I love this! As soon as I found it, I immediately implemented it into my blog and I know that it will be useful. I use to do this by hand!
I found one bug and a slight-bug.
1. Line 380 references “new-window.gif” in the “/wp-content/” folder. This works for someone that has WordPress installed in the root of their site, because this makes the plugin look for http://www.domain.com/wp-content/. But many people put their WP installation into a subfolder, so this breaks the link to the image. The simple fix is to remove the preceeding slash, so that it reads src=”wp-content/new-window.gif”.
2. Any professional writer will be used to using en dashes between sequential numbers instead of hyphens (1–3 instead of 1-3). You may not notice this difference in your font, but it’s there! And because it’s not a regular hyphen, it causes problems for Scripturizer. I’ll play around with it myself, but it would be great if the plugin could read an en dash and convert it to the required hyphen only in the URL. This would allow me to continue being proper in my writing, but keeping the links working. And it would still work for people who type a hyphen.
FYI: type an en dash in Windows with Alt-(Numpad)0150. In Mac OS, it’s Opt-Hyphen.
Oops. Point 1 should actually be:
src=”‘ . get_settings(‘home’) . ‘/wp-content/new-window.gif”
This makes a relative link that should work regardless of where WordPress is installed.
I played with point 2 for a little and couldn’t figure out a solution. It probably has something to do with lines 363 and 414.
Hi Daniel,
Thanks for the encouragement and for the great suggestions. (1) For the image link, I think your second comment has the correct code. I’ve updated the repository, and you can get the code here: http://scripturizer.googlecode.com/svn/trunk/scripturizer.php
(2) On the en dash, I agree with you, but it might take some serious elbow grease to re-vamp the current regular expression. I’ll add it to the feature request list (http://code.google.com/p/scripturizer/issues/list) in hopes that the next major version will allow that functionality.
only by grace,
LO
Laurence,
I just upgraded to 1.6 DEV and now my verse references default to westminster references. See:
http://tatumweb.com/blog/2006/10/03/against-torture/
Rich.
BlogRodent
Hey Rich,
Thanks for the heads up. I’ll add this bug to the task list for a future update.
in grace,
LO
I don’t know if you saw my reply to the default references in the Google repository, just in case not I’ll reply here for anyone who might not follow the links forward to the issues section there.
Comment out lines 425 to 429 to turn off the WSC default. For some reason it resets
the default to WSC there, even if the condition doesn’t match the if statement. I
don’t know enough PHP to figure out why it is doing this.
To comment it out, just add to slashes in front of those lines (as in //)
So it should look like
// //***** Begin WSC hack
// if ($book == (‘WSC’ || ‘Westminster Shorter Catechism’) ) {
// $bible = ‘WSC’ && $translation = ‘WSC’;
// }
// //***** End WSC hack
That should do until there is a proper fix. Technically you don’t need to comment out
the lines that are already comments, however I did to show the whole block is in need
of repair.
As for the options page, on line 75 just change to 1.5a to 1.6 Dev.
The problem has something to do with the logical OR operator. As if I do:
//***** Begin WSC hack
if ($book == (‘WSC’)) { // || ‘Westminster Shorter Catechism’) ) {
$bible = ‘WSC’ && $translation = ‘WSC’;
}
//***** End WSC hack
It works properly as well. Notice the or operator portion has been commented out.
That was what I replied over there anyhow. It looks like the logical OR is setup properly to my eyes, but I am not really a good PHP programmer so I don’t know why it is seeing it the kind of OR it should.
By the way thanks for keeping the work up on it. When I used the original version’s repository I couldn’t find anything new that worked with WordPress 2.1. Then I finally did a search and found this. If possible you should update the original library to point here.
(http://dev.wp-plugins.org/browser/scripturizer was the one the old plugin would point to).
Thanks!,