MyClient V3.1.4 has been released. This is strictly a bug fix release so you only need to update your files. There are no configuration changes to be made.
Enhancements
I've made a few display changes to the CycleLog Calendar. A while back I had update the summary displays to colorize the results and adjusted the fonts. I've now done similarly to the calendar which was kind in a rather confusing and sad state. I've updated the font, added the ride location (Indoor/Outdoor), colorize the text based on that and changed the entry and summary background colors.
So this much needed improvement seems reasonable for now, but I may need to tweak it a bit in the coming days. Another item I will likely need to address is entries for "today". Right now I'm guessing those might still be a bit wacky. I need to wait until I have a ride and time to fix the display for today though. Otherwise it's just a guessing game.
Yesterday a friend at work found that he could force a path disclosure leak on some sites running PolarBlog (and many other application also I would think). This does not pose a danger to your PolarBlog installation, but can provide information which might be helpful if someone were to find a way into your site via a different application.
The quickest and easiest way to prevent this from occurring is to stop PHP from displaying errors to the screen and saving them to a log file instead. This is a very good standard security practice that I've followed for a very long time, and you should too.
If you are running your own server and have access to your php.ini file you likely either are already doing this or should easily be able to make the appropriate changes there. But most people run in a shared hosting environment and will need to do this via a .htaccess file. Information for how to do this has long been in the PolarBlog documentation. It is highly recommended that you read and implement the changes in the .htaccess File section of the PolarBlog Documentation. This will prevent PHP errors from being displayed on your site when any PHP errors occur in any of your PHP applications. Again, this is a highly recommended security practice that will prevent all of your PHP application from leaking potentially exploitable information to those who may wish you ill.
I will release an update soon that will prevent this information leak, although I consider this to be a minor security issue, at least for PolarBlog. But being this information could be leveraged to help attack your system I will be closing this disclosure bug.
Being that I haven't been getting any serious development work done on any of my main projects lately, I thought I'd try to do a rundown of what the future holds for each of them…
CycleLog
Part of me would like to expand the CycleLog to support multiple riders and package it for release. Of all my projects this one is probably the most unique and might be of use to someone else as there are few alternatives available. But alas I already have too many projects going on to keep up with thus I've resisted the temptation. Besides, it meets my needs and I keep adding feature each year that interest me. Maybe someday. For now I'll have to be happy with the updates done in January. The next additions likely will be a bike maintenance log and ideally some ride results graphing. Again, someday.
MyClient
A bug fix release for MyClient was issued in January. The plan is still to eventually add support for simultaneous connections to PostgreSQL databases along with MySQL. Not sure when this will happen, but that's the plan. It's likely that this won't be until I find the time and inclination to do something useful on PostgreSQL. I believe largely it's really just a matter converting one of my current MySQL DB classes to use the PostgreSQL equivalent functions.
PolarBlog
PolarBlog is at a relatively stable state since implementing and releasing Akismet support to augment the comment and trackback RBL system. There's a few minor things I'd like to do, but largely this project is waiting for Yaper 3.x so I can rework it using that templating engine.
Weather
After wallowing around for a good long time, I finally got this documented, packaged up and released in March. Baring a change or addition to the NWS XML feed, this project likely will not be updated anytime soon. It's stable and it works, what more does it need?
Yapter
The V3.0 rewrite is underway, but progress has been slowed by a number of both internal and external factors. I began building the project site and documenting its usage, but in the process I stumbled into a hide() function bug. I last left off trying to fix that problem, but it remains unresolved and I have not had a chance to pursue it further.
As —or lately more of an "if", the weather improves I will be spending more time outdoors and hopefully logging lots of miles on my bike. In turn this means less time for other things, but if I get some issues under control I should still have time to plug along on my projects. That the positive side of it. The negative is that I've spent a lot of time in the past several years dedicated to maintaining multiple projects. Frankly I'm a little burnt out right now and have spent what time I have working on little side project and trying to figure out exactly what to do with my online presence. At some point I think I'd like to split PolarLava in half, leaving the development things here and moving the more personal things to Papendick.us. Again this is just another thing to divert my attentions from my projects. But the time will come when all of the things I would like to do will come to pass. It's all just a matter of having the time to do it and deciding what's most important to me. Because in the end, that's all that really matter, right? :)
It's been largely done for a while now, but I've finally gotten all of the little things done so I can officially release my PHP5 weather class. It's now under version control, has all the API documentation and is packaged up to go. So if this is something that might of interest to you, hop on over to the PolarLava Weather project page.