Once we released 1.0, we did not sit idle. Instead we immediately began work on improving the CMF.
In fact there was such a continuous stream of good ideas and things that felt like a must have, that
we let ourselves slip quite far from our
defined release process. Or lets say we had every intention of aliging ourselves with the Symfony2
core release cycle by releasing within 1-2 months of core which would have meant a 1.1 release in January.
Instead it tooks us 6 months to get to RC1, which on the upside is inline with what we intended for future
As we feared, it turns out that we had to do a few minor BC breaks which we tried to document as much as
possible in the CHANGELOG.md files in the respective packages. We also have updated the documentation already
with lots of details on the new features we added. Unfortunately due to limitation in the current symfony.com
website, we cannot provide a rendered version just yet. So for now please review the
dev branch. Hopefully we will
eventually also be able to provide multiple versions of the CMF documentation just like it is possible for
the core documentation.
Let me briefly highlight some of the key improvements that are coming with 1.1:
A lot of effort was spend in making the CMF more resilent towards edge cases and given better more
helpful error messages.
Support for newer version of Jackalope and PHPCR ODM, that bring lots of bug fixes, speed improvements,
and better debugging and profiling (including Symfony2 debug toolbar support).
The routing system was made even more flexible, meaning there is even less code to write when
implementing a new storage backend. As a result much less code is now needed in SimpleCmsBundle for
The menu system has seen several tweaks, most noteably it is now possible to configure a fetch depth,
which can give drastic performance improvements for deeply nested menu structures.
A new Bundle was added for handling SEO meta data.
A totally reworked Standard Edition that is based on the core Standard Edition to make it easier
to understand what is necessary to add to a Symfony2 application to integrate the CMF.
So what is still left until we can go stable? For now we want to give at least 2 weeks from now to allow
the community to do some testing and to focus on bringing all the documentation up to date. So expect a stable
release at the earliest towards the end of April at the latest sometime in May. Other than this the main
areas where we might still see some changes are:
The Bundle for handling media data might see some more improvements for
handling of uploads.
The Bundle for handling routing might see the addition of a solution to do
batch lazy loading.
The CMF Standard Edition will be aligned more closely with the Symfony2 core Standard Edition.
Updating documentation and ideally figuring out a solution to provide both the 1.0 and 1.1 docs in parallel.
More testing and fixing any edge cases that our users discover.
To get an idea of what is needed to update to 1.1, have a look at the
PR to update this website to the new
version. Also note that the CMF sandbox has also already
been upgraded to 1.1.
We are also very happy with the growing eco-system around PHPCR. Most noteably there is now a
PHPCR shell to interact with a PHPCR repository as well as
finally a PHPCR GUI that supports reading and writing
via a web interface!