The list of new stuff and changes is short but sweet.
I've invented a machine which makes you read this in the voice of Professor Farnsworth!
Jokes aside, there's a new version of the Flux "machine" ready for you on TER. Its version number is 7.1.0 and although it contains mostly bug fixes, there are a few new features worth mentioning here (before actual documentation gets published).
First a very short message: The extension manager update script for Flux now also clears Extbase's reflection and object caches in a safe way. Run it and you should experience zero issues with missing dependency injections, classes not being found and similar class cache issues.
Flux 7.1 is compatible with Fluidcontent 4.0 and Fluidpages 3.0! You can upgrade if your versions are at least those numbers, but earlier Fluidcontent and Fluidpages versions may break.
The build has been confirmed on most recent versions of TYPO3 CMS 6.1 and 6.2 only. Due to recent bug fixes in both versions you may have to upgrade your TYPO3 core as well. The issues which could become present are minor; for example not being able to fetch the correct Flux form when editing an element - no fatal breakage should occur and the core upgrade itself should be completely safe to perform.
Although still fairly basic in nature, there is a much improved support for editing Flux-enabled records in unpublished workspaces. You can make changes, review and publish - but until both fluidpages and fluidcontent are also updated, full workspaces support when editing pages and content is not yet expected. In general, the output should work to let you preview unpublished content and pages - but the editing experience in the backend depends on those coming updates. Until then you may see duplicates of content, deleted content or content not showing up when editing in an unpublished workspace.
A few of the ViewHelpers and their options have been deprecated and changed - we already published a <link http: fluidtypo3.org blog news flux-71-changes.html external-link-new-window>short article about how to proceed with migration and it is still valid. In addition, you can now find this same information as part of the official documentation on this site - in the <link internal-link internal link in current>chapter about migrating to Flux 7.1.
There are two parts to this subject. The first is how Flux's own TCA is constructed - and thanks to <link https: github.com pixelmatseriks external-link-new-window>Mats Svensson from <link http: www.pixelant.se external-link-new-window>Pixelant in Sweden, our relations and localisation support is now 100% native TYPO3 TCA. This means that when you perform localisation of content and pages in Flux 7.1, every behaviour you experience is now governed by the TCA of the system. You can change these options the same way you normally would modify TCA.
The second part is the TCA that Flux is capable of generating for your tables and domain model objects. A new feature has been added which allows you to create Flux Form implementations to use as TCA for your model objects, but without the need for a custom Provider class to return said Forms, and without the need for the Flux annotation-based TCA approach. The benefit of using Flux Form implementations is the absolute control you have over the objects' parameters and structures - and to create reusable PHP objects with full sheets of Flux fields for those properties that repeat themselves throughout your domain.
Although this feature is still so fresh that it is barely documented, there's a <link https: github.com fluidtypo3 flux commit external-link-new-window>very brief example of how to use it. The key to it all is writing a custom object with a custom initialisation method. Hint: the same type of subclassing can be done to create your own types of Sheets, Containers, Sections etc. and passing your PHP class name when using $this->createSheet($type) or $this->createField($type) as value of $type, your class is initialised and is added (along with any children added by that class' initialisation) to the Form structure.
The capability to use such custom objects as Flux forms for domain objects is not new - but the convention-based resolving of Forms for model objects is.
We hope you enjoy the improvements! You can expect updates for Fluidpages and Fluidcontent in the coming weeks, as well as an official release of FluidcontentCore (FCC).
Kind regards,
The FluidTYPO3 team