18/09 2014
Flux 7.1 released

The list of new stuff and changes is short but sweet.

Good news, everyone!

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.

Workspaces support

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.

Minor ViewHelper API change

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.

Improvements for TCA integration

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

 

Archive

09/01 2017
09/11 2016
09/06 2016
21/12 2015
07/12 2015
25/11 2015
25/09 2015
22/09 2015
01/08 2015
10/03 2015
03/03 2015
12/02 2015
25/11 2014
01/11 2014
16/10 2014
02/10 2014
02/10 2014
19/09 2014
18/09 2014
05/09 2014
22/08 2014
02/08 2014
27/06 2014
06/06 2014
13/04 2014
27/03 2014
12/03 2014
11/03 2014
05/02 2014
25/01 2014
17/12 2013
08/12 2013
03/12 2013
04/11 2013
Flux 7.0 Teaser
06/08 2013
21/07 2013
10/06 2013
04/06 2013
01/06 2013
27/05 2013
19/05 2013
19/05 2013
11/05 2013
26/04 2013
30/03 2013
19/03 2013
17/03 2013
13/03 2013
10/03 2013
10/03 2013
05/03 2013
04/03 2013
03/03 2013
02/03 2013
01/03 2013
28/02 2013
27/02 2013
25/02 2013
24/02 2013
24/02 2013
23/02 2013
10/02 2013
03/02 2013
03/02 2013
27/01 2013
Asset management in Fluid
20/01 2013
16/01 2013
13/01 2013
08/01 2013
16/12 2012
25/11 2012
18/11 2012
08/11 2012
07/11 2012
05/11 2012
04/11 2012
28/10 2012
22/10 2012
14/10 2012
13/08 2012
08/08 2012
31/07 2012
30/07 2012
25/07 2012
29/04 2012
29/04 2012
22/04 2012
16/04 2012
21/03 2012
Flux 1.4.0 released
08/03 2012
Flux 1.3.0 released
04/03 2012
03/03 2012
28/02 2012
19/02 2012
A Sneaky Sneak Preview of the next version of Flux
13/02 2012
12/02 2012
06/02 2012
30/01 2012
27/01 2012
15/01 2012
26/12 2011
24/12 2011
11/12 2011
11/12 2011
10/12 2011
04/12 2011
04/12 2011
30/11 2011
26/11 2011
25/11 2011