Announcements

Today we released vfsStream 0.11.1 which contains an important bugfix for usages of mkdir(). Until 0.11.1 calls to mkdir() with vfsStream URLs replace already existing directories or files, instead of returning false and trigger a warning. This has been fixed with 0.11.1. Thanks to Julien Fontanet for reporting the issue.

As always you can get the new release via our pear channel.

Some minutes ago vfsStream 0.11.0 was released with several bug fixes and new features. Unfortunately this introduces a BC break to the vfsStream::create() method introduced with 0.10.0. While in 0.10.0 it completely replaced the directory structure this is not the case any more. It now only adds the given structure to an existing structure, either to the directory given with the second parameter, or to the root directory without removing any other childs of the root directory. If you want to replace the whole directory tree you can use the vfsStream::setup() method which now has a third parameter. See create complex directory structures documentation for code examples.

Another new feature is the possibility to import a file system structure from disc into vfsStream. This way you can emulate an existing file structure in vfsStream without having to recreate it from scratch. See copy from file system documentation for more details.

Additionally, three bugs were fixed: unlink() does not remove non-empty directory any more, vfsStreamDirectory::hasChild() now doesn't give false positives for nested paths (patch provided by Andrew Coulton), and opening a file for reading only doesn't update the modification time any more (initial patch provided by Ludovic Chabant).

Thanks to all contributors and issue reporters for their help to improve vfsStream.

As always you can get the new release via our pear channel.

Today vfsStream 0.10.1 has been released, containing two bug fixes. The first was a problem with the vfsStream::create() functionality introduced with 0.10.0, where using numeric directories failed because of implicit type conversions (in PHP) and explicit type checks (in vfsStream). Thanks to Mathieu Kooiman for finding this issue and providing a patch.

The other fix is a mix of a documentation and type hinting fix: now you can only use directories as root instance - before it was allowed to add files as vfsStream root with with vfsStreamWrapper::setRoot(), however this failed latest when trying to access other files with a directory name. Starting with 0.10.1 you can not add files as root any more, and this was also used to change the return type documentation so you can get better auto completion when retrieving a directory object with vfsStreamWrapper::getRoot(). Thanks to Dmitry Kabanov for reporting this issue.

As always you can get the new release via our pear channel.

Not even ten days after the release of vfsStream 0.9.0 today the fresh version 0.10.0 hits the streets, containing various improvements to make your life with vfsStream much easier. Especially when you want to create more than just two or three files it's really noisy to create the directory structure. To ease this vfsStream now provides a vfsStream::create() method which accepts an array and builds the directory structure from it. See create complex directory structures for more details.

Another improvement is that vfsStream now supports flock() meaning that you can call flock() with a vfsStream file url and afterwards check the file instance whether the lock was set correctly. Another requested feature was the possibility to print out directory structures, but I had the idea of providing even more possibilities on what you could do when inspecting the directory structure. For a more detailed view on what this new feature provides check the wiki page about Visitors.

Also this release introduces a BC break. As announced with 0.9.0 the then deprecated method vfsStreamContent::setFilemtime() was removed now - please use fsStreamContent::lastModified() instead.

In order to ensure better compatibility between PHP 5.2 and 5.3 calling support for stream_set_blocking(), stream_set_timeout() and stream_set_write_buffer() on 5.3 was added. However calls with these functions always return false and do not have any influence on vfsStream, which is rather because concrete usage scenarios are a bit unclear at the moment. If you have any ideas or feature requests on how vfsStream should treat such calls feel free to add your comments on issue #15.

You can get the new release via our pear channel.

Today we released Stubbles 1.6.0, which is another major step of abandoning our XJConf for PHP dependency. The variant manager configuration can still be done using XML, but we don't use XJConf any more, but an own parser which is much simpler and uses less resources. It is not as powerful as XJConf, but powerful enough for all features required for variant configuration, and still being able to extend this configuration with user-defined tags. So the 1.6 series will also be the last one where XJConf is bundled. In the 1.7 series XJConf will not be part of the release any more, and all XJConf related code will be moved into a separate project.

Another improvement is the fact that there is no need any more for specific annotation classes. If no specific annotation class is present the new stubGenericAnnotation class will be used. This is sufficient for most use cases, and Stubbles will only use the new generic class internally.

One last improvement is the possibility to use injection providers for constant values as well. Until now it was only possible to set a concrete value for a constant, but starting with 1.6.0 it can now be bound to an injection provider which may calculate the value at runtime or use other classes to retrieve the actual value.

See the full changelog for all details of changes for this release.

To start with the Stubbles 1.6 series the first release candidate 1.6.0 RC1 is now available:
http://downloads.stubbles.net/rc/stubbles-1.6.0RC1.tgz

Please test it thoroughly with your applications and report any bugs into our Trac installation.

For a list of changes please see the changelog.

If no obstacles rise up the scheduled release for 1.6.0 is March 8th.

Today we released Stubbles 1.5.1. This is a bugfix release, fixing one bug inside the XML/XSL view engine that prohibited usage of the common page path for including xsl stylesheets from the common project. You can get the release from our downloads page.

A new year, a new minor release. With Stubbles 1.5.0 we continue to adhere to our release early, release often approach. The release contains further improvements on our IoC feature, as well as API improvements for various classes in the ipo package. A major change however is that we discontinue to provide several different versions of the release. Until now, all releases contained various packaged versions of the framework classes inside the lib directory. This has changed, starting with 1.5.0 we only provide the stubbles.php file. For a full list of changes please see the changelog.

But we don't stop at this point. Work on the 1.6.0 release has already started and will see tweaks to how we use annotations. But more on this in a separate blog post coming soon.

On the last day of 2010 the probably last releases of the Stubbles 1.3 and 1.4 series are now available: releases 1.3.4 and 1.4.4. Both contain bug fixes for handling of variant cookies so that detecting a variant from cookies now works properly.

You can get the latest release from our downloads page.

Today we released Stubbles 1.3.3 and 1.4.3. The releases include improvements for the XML/XSL view engine. One of them is the removal of a required xsl-imports.ini configuration file if only the default imports should be used - as the engine would not work without the default imports properly the configuration file needs only to be used if there are additional user-defined XSL stylesheets to be imported.

The other improvements revolve around the variant support. Until now the cookie which stores the variant was not re-evaluated when the variant configuration changed. This is different now, as the name of the variant configuration is now stored in another cookie. If the name of the variant configuration changes the variant cookie will not be used to determine the correct variant for the user. This means the user will get a fresh new variant, even if he has the name of an older variant in his cookie and the old variant is still configured, which is especially useful when starting a new variant test.

In order to ease selecting the correct variant when working in development or stage mode, especially when it comes to random variants, the stage assistant now contains a variant selector which can be used to change the current variant of the website.

You can get the latest release from our downloads page.

Today we released the bugfix releases Stubbles 1.3.2 and 1.4.2. The releases fix a bug with the rdbms pdo implementation which caused a fatal error when trying to fetch a column on a result set. The other fix is for the stubProperties class where iterating over the sections was broken causing that after a first iteration the internal pointer was not reset to the start when starting the second iteration. Get the releases from our downloads page.

As described in a previous blog article Stubbles did not work on PHP versions built using libxml 2.7, which is the case for at least all PHP versions since 5.3.0. We fixed the issue and make it today available as a bugfix release. This means that both 1.3.1 and 1.4.1 can now be used on PHP 5.3. See the changelog for a complete list of changes. Additionally we started to provide an Upgrade Guide with more detailed instructions on what needs to be done when upgrading from a previous version.

With the release of vfsStream 0.8.0 the status is now beta instead of alpha as it was before. New features include a umask simulation which allows you to set a umask for vfsStream URLs which is then applied for new directories and files, except if you explicitly set the permissions of a file or directory using the vfsStream API. To be backward compatible and easier to use the default umask is 0000 - so if you are not interested in using this feature just don't use it and everything stays at it is.

Another new feature is the support of .. in URLs, provided via patch by Guislain Duthieuw, which means you can now have constructs like vfs://root/path/../otherpath which is mapped to vfs://root/otherpath. However, realpath() still doesn't work - there is no way to make this work with how realpath() is currently implemented in PHP itself.

Besides this two bugs have been fixed, one where it was impossible until now to access a child of a directory via the vfsStream API if the child name is contained in the parent's name. The other one was an incomplete error message when you tried to access non-existing files on the root level.

You can get the new release via our pear channel.

Today we released Stubbles 1.3.0 and 1.4.0. First, what's new in 1.3.0? This release features a new API for the request interface which is much simpler to use. There are now separate methods for accessing parameters, cookies and headers, and the way to filter and validate request values was very much simplified. For more details on how the new API looks check the rewritten Wiki manual. All old methods are now deprecated.

Another change is the replacement of XML configuration via XJConf for error messages and route configurations. Both are now configured via property files. The old way of configuration via XML files is still available but has to be explicitly activated. However, it is deprecated as well. This is in compliance with our strategy to remove the dependency to XJConf from Stubbles.

Up to 1.2.0 we shipped minified versions of the JavaScript files delivered with the release. Starting with 1.3.0 we don't ship those any more, instead we recommend the usage of Minify which will take care of minification, and much more you would like to have in you application, like using 304 status codes, compression and pulling all JavaScript files in one request.

The REST processor now supports filter annotations for REST method parameters. This is useful to validate such input values in the surrounding code, and to keep the business code of the REST method free from validation code.

In several different classes we added various methods for easier usage. See the changelog for a complete list of changes.

What's new in 1.4.0? Well, not that much. Basically, 1.4.0 is the same as 1.3.0, but with all code removed which became deprecated in 1.3.0. So, which version should you upgrade to? If you want to upgrade fast and only want to profit from bugfixes we recommend upgrading to 1.3.0 and activate the XML configuration. You might also want to change your route configuration files (and error message configuration files if you have any) into the new ini format. It is also recommended to upgrade to 1.3.0 before starting to migrate to the new request API. Upgrading to 1.4.0 should be done after all request API dependent code was migrated to the new methods and there are no calls to old methods left. We recommend to aim for migration to 1.4.0 as the next minor or major version will be based on 1.4.0 - deprecated and removed code will not return any more.

Until we release the next minor or major version we will continue to support 1.3.0 as well as 1.4.0 which means bugfix releases will be done for both minor versions.

Today marks the day of the release of Stubbles 1.2.0. This release features improvements for the XSL view engine, namely introduction of support for bot link cloaking, and the handling of the session id as a normal request parameter instead as part of the path. Additionally, if a user agent is now recognized as a bot the link creation functionality of the stub:link template will not add the session id to the created URL. This is applicable for user agents only which are not recognized as bots and which do not support cookies. All of this should help applications build on Stubbles to be more SEO compliant and should help improve the search indexing from search engine bots.

As this is a major release all code which was deprecated with 1.1.0 was removed. If you still rely on interceptor and database configurations in XML, now is the time to upgrade both to property file based configurations.

With the addition of Romanian translations for error messages delivered by the framework Stubbles can now be used for Romanian applications out of the box.

For a complete list of changes please consult the changelog. You can get the release on our downloads page.