ProcessWire 3.0 Alpha 1 is here, with promises of its own namespace, multi-instance support and more. There have also been improvements made to the current version of ProcessWire, via version 2.6.20.
As far as a release date is concerned, the ProcessWire team has simply said that a stable release won’t be available until spring 2016.
What’s New with ProcessWire 3.0?
At this early stage, ProcessWire 3.0 is identical in functionality to the current dev branch (2.6.20).
However, it differs greatly on the code side:
ProcessWire 3.0 runs in its own PHP namespace. Previous versions of ProcessWire ran in the root namespace.
It supports the ability for modules to optionally use alternate namespaces. Modules that use dedicated namespaces also benefit from more autoloading options.
Multi-instance ProcessWire support is partially there already, though not quite ready for you to use just yet. What is multi-instance support? That means you can have one script that’s issuing API calls to multiple installations of ProcessWire, different databases, and so forth.
ProcessWire have done a lot of code cleanup, getting rid of old-style API calls, deprecated methods and more.
Composer support is partially there and in progress.
According to ProcessWire, “the above [list] is how this version is different now, but of course there’s a lot more on the way”.
As many readers will know, CMS Critic is currently powered by ProcessWire, and as a free and open source project, we’re always eager to see how it evolves at a platform.
And as always, be sure to check out ProcessWire through our CMS Directory.