In case you haven't already read, there's a pretty serious vulnerability related to XML-RPC in some PHP applications including Serendipity.  Read more at hardened-php.

This class, cleverly named PHP Input Filter, definitely merits further investigation.  It filters input to prevent Cross-site Scriptin Attacks.

My simple calendar class is being used here: Alaska State Hospital and Nursing Home Association (ASHNHA.com)

A number of posts out there today concern working with HTML forms in PHP (Paul M. Jones » Form Processing Questions). The debate seems to hinge mostly on whether a single monolithic, automatic form generation class/script should be preferred to an approach that separates the Model and View more cleanly.

I didn't want to let Sandy beat me to the punch this time so here goes. Over at Forum One, my employer, we released Syntax CMS version 1.1.0, which is the content management application that we've built and use. The code has come along way over the last few months in response to features requests we heard from multiple clients.

One of the things I have found that irritates me needlessly are people who are impatient debuggers. Finding and fixing bugs is certainly one of the least enjoyable activities you have to put up with when writing code. It takes a certain amount of persistance for going through the code to make sure you're understanding what it does (not what it's supposed to do) balanced against knowing when to ask for help or a second set of opinions. A quick search of the web didn't turn up many non-technical tips about debugging scripts.

I wanted to recommend two php applications that I recently setup for our own use and was very impressed by them. One of the biggest things that impressed me about both was how ridiculuosly easy each one made the install process. Something we need to improve for the Syntax CMS open source projectwe use at work.

The framework and content management system we develop and use at work has been nominally Open Source for over a year and a half. Over the last month, we've made substantial performance and feature improvements to it and are preparing to make an official 1.0 release very soon. We've set up a blog, initially for our internal use, but its open to the public at syntaxblog.forumone.com

Mike Cogan wondered on his blog why php is more popular than java. Most of his argument seems to be based on the assumption that PHP coders want to get a website up and running as soon as possible with no regard for proper planning and design. Somehow, simply choosing to use Java makes you plan and design better. Huh?

Looking to boost your php application's performance. Check out memcached, a distributed memory object cache. It has hooks for PHP, Perl, and Java so you can share cached objects among scripts in multiple languages.