New Usage Instructions and WP 2.1 Compatibility Notice March 2, 2007
Posted by LO in Development.trackback
Dear Scripturizer users,
I have added a new page to explain how to use Scripturizer’s features. So far I have instructions on how to create links using both your default Bible version and user-specified versions. (Please know that you can set your own default version to any of the supported versions listed on this page.)
In the near future I will add further instructions on how to use the ESV “get verse text” feature. (Which, speaking of this feature, I am hoping to re-program it along the lines of Simon’s nice Ajax-powered ESV technique in the next Scripturizer release.)
WP 2.1 Compatibility Notice
I have not yet thoroughly tested Scripturizer on WP 2.1. I think it should work just fine in dynamic mode, as opposed to static mode. But again, I have not tested it thoroughly. For the time being, I recommend not using static mode.
If you are running WP 2.1 please let me know if you have success or find problems with the Scripturizer plugin.
by grace,
LO
μόνος δοῦλος
I’m not having any problems in 2.1.2. I’ve also added an option to scripturize excerpts selectable in the admin panel.
Unfortunately, I must report problems. I use Scripturizer 1.5 in static mode; and after upgrading WordPress to 2.1.x, I got weird MySQLerrors after posting if I used accents (i.e., á, é, í, ó, and the such). Problem is, that happens very often because I have to type words in Spanish.
Anyway, thanks a lot for Scripturizer !
Eduardo,
Sorry for the difficulties. I wish I could speak Spanish, but I’m afraid I have no Spanish programming experience.
I would recommend either (a) using static mode in Scripturizer 1.5 or (b) trying Scripturizer 1.7.
LaurenceO, thanks for the message. In fact, my blog is written in English (check the link); but sometimes I have to type the occasional Spanish word scattered here and there, and that’s when my Scripturizer (1.5) goes crazy.
Thanks again for Scripturizer. I’ll try the 1.7 beta and I’ll see how it goes.
I’m slowly learning more about encoding for multiple languages. If I figure out how to release a multi-language edition, I’ll post the details on this blog….
(And if anyone has any tips on how to encode PHP scripts for German, Spanish, etc., please let me know.)