PolarLava::Blog

The latest update to my CycleLog adds graphs for the distance, average and maximum speed.  You will find these graphs on main, calendar and search pages.

At this time on the main page I'm not graphing the "Lifetime" section as the amount of data requires this to be a tremendously large sized image in order for this to be readable.  It's largely more for my current rides as you'll note on the calendar pages.  But it's also a nice feature to have on the search page although depending on the data set, it can take up to 30 seconds to generate the image.  Thus in most places the image is cached with the notable exception of the current month on the calendar page.  The intent is to eventually graphing of the year on the main page as well as on the Yearly Summary page.  A lot of that will depend upon finding a suitable image size that will allow the data to be displayed but still maintain a reasonable file size.  Being historical data I will only need to actually generate them once with the exception of the current year.  And that will need to be generated a separate process as it takes too long to generate as part of the page generation.

I'd also like to take a moment and give a quick nod to JpGraph which is what I'm using to generate these images.  I can't begin to say enough good things about how easy and flexible the application is.  I'd highly recommend it to anyone who is looking to do (a wide variety) of graphing.

MyClient V3.2.1 has been released.  This is release only requires file updates, there are no configuration changes to be made.

Enhancements

• None

• Bad include path for session and serialize data support has been corrected.

• None

• None

MyClient V3.2.0 (Bluefin trevally) has been released.  This is release only requires file updates, there are no configuration changes to be made.

Enhancements

• Updated to operate with E_STRICT error_reporting.
• Added support to display serialized and session data.  When enabled, data that is stored in a session format (e.g. using a DB backed session handler) or data that is serialized will be displayed in a more readable unserialized fashion.  Using this option will automatically enables the "Render HTML" option so this option displays properly.

• None

• None

• RENDER_SERIAL

PolarBlog V1.10.2 has been released.  This is a bug fix and performance improvement release.

Enhancements

• Improved query topic indexing.
• Improved comment indexing.
• SafeSQL*.class.php Added released NULL support and fixed PHP5 abstract method declaration error.
• E_STRICT Compliance: Fix Call-time pass-by-reference errors.
• E_STRICT Compliance: You need to set your default timezone via date.timezone.  See PHP: Date and Time Functions, PHP: Appendix J. List of Supported Timezones and the .htaccess File section of the PolarBlog Documentation.

• Entries in deleted topics causing the entry index page to fatal.
• Search results not being properly sorted, partially due to V1.9.1 change to prevent memory overload.
• New and updated entries that are post dated shouldn't ping Ping-O-Matic (if enabled).

• None

• None

I've been quite busy as usual the past few months, but with the weather declining that generally means good things for my website and software development.  Anyhow, a few weeks back I discovered that the last PolarBlog release broke the "Entry Index" page.  And I've been struggling to understand why the search function became so horribly wrong most of the time.  Well, I finally got tired of dealing with it -because I search my own blog often, and tracked down the problem last night.  It seems some dummy broke it as part of his efforts to fix a poor architectural decision at the very beginning.  Thus it actually broke back in V1.9.1.  And I've been doing some cleanup work so it now runs without complaint under E_STRICT.

So hopefully I will find time over the long weekend to get an update packaged up and released.  :)