I recently released Slim Framework 2. This is a radical departure from past versions. Version 2 introduces PSR-2 compliance and PHP namespaces. It requires PHP 5.3 or newer.

The next version of the Slim Framework will introduce PHP namespaces and PSR-2 compliance. Because this is a large departure from the past, I will tag this version “2.0” when it is released (soon).

I’ve just released Slim Framework 1.6.7. This minor release is recommended for everyone and includes the following changes:

I’ve just released Slim Framework 1.6.6. This minor release is recommended for everyone and includes the following changes:

I’ve just released Slim Framework 1.6.5. This minor release is recommended for everyone and includes the following changes:

Now you can instantly launch new Slim Framework applications on PagodaBox with the official Slim Framework quickstart. You don’t have to worry about creating filesystem directories, downloading and installing the Slim Framework libraries, or messing with complicated deployment routines.

After launching a ton of Slim Framework applications, I grew tired of re-configuring the same filesystem structure, the same libraries, and the same boilerplate code time and time again. No more.

I’ve just released Slim Framework 1.6.4. This minor release is recommended for everyone and includes the following changes:

I’ve just released Slim Framework 1.6.3. This minor release is recommended for everyone and includes the following changes:

I’m happy to announce that the Slim Framework now works with Composer and is available on Packagist. Andrew Smith at Silent Works has written a tutorial that demonstrates how to use Composer and Packagist to manage dependencies in your Slim application.

I’ve just released Slim Framework 1.6.2. This minor release fixes a bug with Flash messaging when used with the session cookie middleware. I strongly encourage you to upgrade your Slim 1.6.x applications to this version.

I’ve just released Slim Framework 1.6.1 into the stable branch. This release includes several bug fixes and general improvements to the recent 1.6.0 release. Changes in this version include:

I’ve just released Slim Framework 1.6.0 into the stable branch. This is a major release and includes a brand new framework architecture based upon the Rack Protocol.

The Slim Framework website is now hosted with Pagoda Box. I’m super excited about the move. If you haven’t heard already, Pagoda Box is a PHP PaaS that provides a very flexible and scalable architecture for your PHP applications.

Today Slim was mentioned by Lorna Mitchell in her latest opinion piece for .NET Magazine that analyzes the current landscape of PHP frameworks. Head on over to read her article, Land of a Thousand Frameworks.

The Slim Framework for PHP 5 version 1.6.0 (currently in the develop branch) introduces new middleware that will automatically parse the HTTP request body based on its content type. This middleware will parse HTTP requests with a JSON, XML, or CSV content type. To enable this middleware, do this:

Thus far, the Slim Framework’s version numbers have mostly adhered to the major.minor.revision scheme. However, sometimes the version numbers have strayed from this practice. Slim is my first large open source project, and it is an ongoing learning experience for me as Slim’s user base continues to flourish.

I am happy to announce that Slim’s support forum and knowledge base now run on Tender™. We previously used the Vanilla forum software, but it proved unstable and unreliable for many users. I want to extend a big thank you to Tender for setting up an open source account for us. Our initial impression is that it is a phenomenal platform, and we cannot wait to put it to good use.

The Slim Framework documentation has moved into the Git repository as of v1.5.2 (currently in the development branch). This change makes it easy for the community to suggest additions or changes to the framework documentation.

The Slim Framework v1.5.2 introduces a new architecture. Several other features have changed and improved. This is a large update and is currently considered beta. Use this version at your own risk. It will remain in the develop branch until users have had sufficient time to vet the new version with their applications.