22/10 2012
Flux 4.7.5 and FED 4.7.7

Bugfixes, two small additions and one UI change

Dear developers,

Flux 4.7.5 and FED 4.7.7 have hit TER. Although they are both mostly bugfix releases, there is one important change that you should be aware of.

Page Template selection and Page Options moved to "Appearance" tab

Quite simply the fields for FED's page implementation have been moved to the appearance tab (as part of a bugfix to get closer to standards). The same fields are there, just alongside other appearance-related fields.

If you are not a fan of this particular change you can restore the old behaviour from any extension's (i.e. your content element / page template provider extension) ext_tables.php file. Just add these lines:

$before = '--div--;Page Template,tx_fed_page_controller_action,tx_fed_page_controller_action_sub,tx_fed_page_flexform,--div--;LLL:EXT:cms/locallang_tca.xml:pages.tabs.options$remove = 'tx_fed_page_controller_action,tx_fed_page_controller_action_sub,tx_fed_page_flexform,';
$GLOBALS['TCA']['pages']['types'][1]['showitem'] = $before . str_replace($remove, '', $GLOBALS['TCA']['pages']['types'][1]['showitem']);
$GLOBALS['TCA']['pages']['types'][4]['showitem'] = $before . str_replace($remove, '', $GLOBALS['TCA']['pages']['types'][4]['showitem']);
unset($before, $remove);

This will reposition the fields into the old position, completely restoring the old behavior.

In addition to this change there are two new additions to notify about:

Argument "sortFlags" for Data/SortViewHelper

This addition lets you influence the way sorting is performed in the same way as SORT_FLAGS would do in functions like sort() or krsort(). The value must be the UPPERCASE_UNDERSCORED name of the constant you want to use (fx SORT_REGULAR, SORT_NUMERIC or SORT_NATURAL). Makes particular sense when used with numeric sorting that might not be sorted correctly using default SORT_REGULAR.

Argument "contentUids" for Page/RenderContentViewHelper

This new argument lets you provide an explicit list of content elements to be rendered. The argument is an array and can be used like {0: 123} to render content element with UID 123. This argument was added to allow a very particular usage: letting extension developers create record types which have inline relations to tt_content and need to render these elements when the object related to this record is being rendered in Fluid. I recently used this in a project to use full content elements as help texts - which would allow an editor to replace a traditional piece of help text with, just for example, a video from youtube. Since TYPO3 internals are used to do the rendering itself these specially rendered content elements would also use any stdWrap you apply, respect group access, start/stop-times and every other content setting.

Then the bugfixes

Some users have reported problems with the ConfigurationProvider logic - these problems were hindering functionality in custom ConfigurationProviders and the FED Page feature (which uses a custom ConfigurationProvider). Those of you who have had problems with 4.7.6 should see all of these problems fixed when installing this version.

Cheers,
Claus

 

 

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