PolarLava::Blog

So after clearing numerous other things off my plate and avoiding being derailed to work on Papendick.us, I've finally started work on the Yapter templating engine.  Nothing too exciting yet, but I have done the first round of code cleanup and internal documentation.  But before this sees the light of day I have a number things I'd like to do…

• Fix the error reporting so it doesn't spew errors to the screen unless you want it too.
• Debug and hopefully fix a couple of reported bugs.
• Add the ability to parse included templates.  (Currently it only allows static content in includes.)
• Build out the new project homepage.
• Rewrite the tutorial/example/documentation.
• Likely many other things I haven't thought of.

A long time ago I sent a version of this single page flush modification to Jean-Pierre Deckers the author of jpcache.  He replied that he would incorporate this change in a future version.  Unfortunately this project has not been updated in a very long time.  Thus I've opted to release this modification directly.  At the time I sent this to JP, he had a concern regarding the flush value being fixed for all installations.  That issue has been corrected in this modification.  So what does it do?

If you use jpcache, you likely know one of the downsides is when you update a page, your changes won't be seen until the cache expires.  That might be alright in some cases, but what if you want it flushed immediately or worse, what if it's a non-expiring page?  Enter the single page flush.  The single page flush option allows you to pass a GET parameter (?flush=1 by default) to a cached page which then forces it to be flushed from the cache immediately and allows a modified page to be quickly and easily updated.

If this sounds useful to you, you can download jpcache V2.1pl here.  This is a drop in place replacement for jpcache V2.  The setup and operation is exactly the same with the exception of $JPCACHE_FLUSH_KEY being added to the jpcache-config.php file.  You simply need to setup this file the same as you have it for V2, add a unique value for $JPCACHE_FLUSH_KEY and then use ?flush=$JPCACHE_FLUSH_KEY value to flush a specific page.  Enjoy!

PolarBlog V1.10.0 has been released.  This release provides additional comment and trackback spam protection and miscellaneous bug fixes.

Enhancements

• Added support for Akismet via PHP5Akismet.  This requires a WordPress.com API key and will only work if you are running PHP5.  More information regarding this feature can be found in the Akismet for PolarBlog entry.
• Added support for autolinking to topics in entries via "[T:tid:optional link text]" format similar to which currently exists for entries or comments.
• Add RBL Admin table entry counts.
• Added session for all visits and IP logging within session.

• Validation fails on some foreign characters in title, post_by and name.
• Stray "]" left after auto linking text on every 4th autolink in an entry.
• When using only images for prev/next, they are locked to 16x16.
• Change RBL IP lookup to robtex.com because samspade.org disappeared!
• Sometimes the session cookie appears to not set and actions after login fail.
• Throwing undefined topics warning when DB connection fails.

• The default value of RBL_IP_WHOIS has been changed per the above noted bug fix.
• Added RBL_AKISMET_KEY
• Added COMMENT_MAIL_RESTRICT

• None

MyClient V3.1.3 has been released.  This is strictly a bug fix release so you only need to update your files.  There are not configuration changes to be made.

Enhancements

• None

• Saving query results in any manner now functions.
• HTML entities in the query window are now properly handled on page reload.
• Two new language strings were added for text translations that were previously missed.
• Database class files have been updated with several miscellaneous bug fixes.

• None

• ERROR_O_NOWRITE
• ERROR_O_NOSAVEFILE
• EMAIL_BODY_RESULTS

A couple of slick changes —well at least I think they are slick, to the CycleLog.  I've now added "Previous" and "Next" to the Latest Ride, Random Ride and Search when individual rides are displayed.

Additionally these same pages now also include a "Other rides on this date…" section if other rides are found on the same (month and) day.  This is a handy way —again, for me anyway, to quickly find and compare rides at the same point in the season in previous years.

Additional changes are also planned and this entry will be updated as appropriate when necessary.

——

1/13/07

Some dummy had this under the "Beer!" topic.  ;)

I've now changed the data display font to a fixed width font and data is now colorized.  Blue=indoors, green=outdoors and red=total in most summary displays.  On individual rides I've opted to use red.  Probably not completely done playing with the layout/color/font thing, but it's pretty close I think.

——

1/21/07

I've finally added a Bikes page to the CycleLog.  This is something I started working on several months back, but it was shelved while I attended to a number of other matters.  I'm happy with it as it is, but at some point in the future I would like to expand it to include a photo of each of the bikes.  But that will have to wait until I actually have some photos of them!