Several new tutorials, components, news and helpers have been posted to The Bakery, the CakePHP community site lately. Here's a sampling:

• CakePHP on IIS6 with FastCGI, SQL Server 2005, and ISAPI_Rewrite
• Filter Out Unnecessary Recursive Relationships
• Twitter Component
• Chartable Behavior
• Increment Behavior
• markItUp! jQuery universal markup editor Helper
• The CakePHP Blog Tutorial with SMARTY
• Vendor Branching
• CakePHP 1.2 stable coming soon

Check out The Bakery for more great CakePHP-related goodness.

Felix Geisendorfer has posted an announcement to the Debuggable blog about the upcoming stable release of the next major version of the CakePHP framework, version 1.2.

The CakePHP team is gearing up to finally push out a stable 1.2 release! If you are following the trac timeline you can see that everybody is putting in huge amounts of work to fix bugs and get everything stable.

He suggests a few ways to get involved in helping to push this release out the door like writing test cases, showing how to replicate bugs and help out the documentation team with their efforts to keep the manual up to date.

On the SaniSoft blog today, Tarique Sani has a quick hack for CakePHP users needing to transition over from the deprecated vendor() call - import().

Use of vendor() function to load third party libs in CakePHP has been deprecated for some time now... It has been replaced with the more generic App::import() the usage is simple.

There's also a little trick you'll need to know for files with underscores (drop it and replace with an uppercase) and how to get it to be a bit more flexible and recognize vendor files in subdirectories or ones differently named.

New on the Debuggable blog today there's this post from Tim Koschutzki about a new feature he's contributed back to the CakePHP project. It allows you to run tests on the command line without having to worry about loading up a web interface to check your code.

It allows you to run all of the following: all core testcases at once, all core test groups, each core test case individually, all application-specific testcases at once, all application-specific test groups and each core test case individually. It also supports plugins, which means you can run plugin cases and groups.

He includes some samples of how it works - a few command line calls and what the output looks like.

In a recent post to the Ask About PHP blog, there's a quick "first look" at the CakePHP framework from a beginner's perspective.

Finally, I found some time to take CakePHP for a spin. I've heard some really good things about it, and I've been trying to get some time to try it out. I installed the framework and went through the tutorial on building a simple blog application. I have to say I'm quite impressed.

The post briefly introduces the Model-View-Controller method the framework follows and shows some of the features/benefits it brings with it - the low entry level, its speed, and whether or not it makes for a good "first framework" for other developers.

On the Debuggable blog, Tim Koschutki has posted the first part of a series looking at unit testing the CakePHP framework. This first article introduces you to the idea of unit testing to help lay the foundation for what's to come.

So you want to read up on Unit Testing in CakePHP? That is great, testing can be such a help in finding bugs. [...] Surprisingly, many people do not know yet what unit testing is. In this first part of a whole series you can get a good grasp of what it is and is not.

He goes over the basic concepts behind the testing - setting up test cases, comparing results, automating them and how they related to code coverage. He gets into more detail with a list of the assert functions (like assertNotEqual or assertClone) and some examples using the simpletest unit testing software. He wraps it up by listing some of the benefits of unit testing, the limitations of it, TDD and what Mock objects are.

The Bakery (the CakePHP programmer's resource) has a few new articles, tutorials and components that have been posted lately. Here's the list:

• Preview and alter the SQL generated from Model::find()
• After 3 years, looking back and moving ahead
• Encrypted Cookie Component
• Open Flash Chart Helper: draw charts the Cake way
• Maintaining an Application-independant Code Library
• Rolling you own Gallery2 component
• DarkAuth v1.3 - an alternative Auth
• Easy AJAX Pagination Using JQuery

Be sure to check out the rest of The Bakery for more great CakePHP-related content.

In a new post to the Debuggable blog, Tim Koschutzki talks some about the work he's been doing on the code coverage analysis for the upcoming CakePHP release:

There are several different kinds of criteria to code coverage. The two most important ones are line coverage (or statement coverage as wikipedia puts it) and path coverage. [...] So how is it going to work? Pretty simple actually. Whenever you run a CakePHP test case Cake assembles information in the background about which lines of your subject-under-test are called.

He includes a few screenshots of the code coverage being run and the end result of the runner with the percent covered.

If you're a CakePHP user and have been frustrated by how this "bake" functionality doesn't allow for more than one validation rule on a given field, check out the new post on the SaniSoft blog (from Amit Badkas):

This is not much of a problem if you have only a few models but when you start to work on several dozen models in a project it becomes very tedious to open each and every model file to make changes.

The result of his frustration has come out in the form of a patch as a part of a new ticket in the CakePHP request submission process.

On the SaniSoft blog, Tarique Sani talks briefly about some of the prefix "automagic" that's already built in to the CakePHP framework's routing.

There are times when you need more than just admin routing, how about something like http://blah.com/user/profiles/edit and http://blah.com/user/profiles/changepassword ? If this could be routed to an action like user_add and user_changepassword wouldn't it be great!! (eg: think ownership ACL checks)

Good thing the CakePHP developers already planned for something like this - they included the connect() method for Router objects that maps the URL request to a method with that same prefix in the controller.