02/08 2014
Flux 7.1 status update

The coming minor update to Flux is almost ready but still has some pending issues to be fixed. You can help!

We are currently working to complete the next stable release of Flux - which will be version 7.1. It will, as is almost tradition by now, be accompanied by releases of both fluidcontent and fluidpages. Simultaneously, but not being a dependency, we are almost ready to release VHS 2.0 and fluidcontent_core 1.0. But we need your help identifying and fixing remaining issues in these important areas:

Workspaces support

Flux 7.1 will feature workspaces support but is still affected by a few issues which prevent usage of workspaces along with Flux in a production context. You can view the current status of this feature support at <link https: github.com fluidtypo3 flux issues external-link-new-window>github.com/FluidTYPO3/flux/issues/627.

Translation and record update handling

We have ironed out most of the bugs related to record update handling - in the context of localisation, record moving/copying and handling of relations associated with records. A number of dependency TYPO3 core bugs have been fixed recently and we await version 6.2.5 which should contain these fixes - so when this version is released, or if you use the git master of TYPO3, please test and give any input you may have for issues listed at <link https: github.com fluidtypo3 flux issues external-link-new-window>github.com/FluidTYPO3/flux/issues/573.

FluidcontentCore - CSS Styled Content replacement

Strangely enough, although a replacement for css_styled_content is often requested, we have had very little input on our call to obtain input in the configuration and templates we intend to ship with this extension on first release. The risk we run by releasing such an extension without proper input about regularly encountered use cases, is that we will have to introduce breaking changes in the next iteration - and we would very much like to avoid that. So give the extension a spin and report your wishes at <link https: github.com fluidtypo3 fluidcontent_core issues external-link-new-window>github.com/FluidTYPO3/fluidcontent_core/issues/35. Note: it's a very specific type of feedback we are looking for, as the issue describes.

Please consider spending an hour or two of your precious time to help us not only improve Flux and the other extensions, but also to help us release Flux 7.1 and the much awaited FluidcontentCore sooner. If possible, please assist with patches - but more importantly: please report issues/wishes and test the code on your own setups.

Thanks!
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