[TYPO3-core] RFC: #10533: Allow predefined setting for "extended view" in list module

[Jörg Klein]

Hi!

"Christian Kuhn" wrote:
> Hi,
>
> General +1 to a patch here.
>
> I agree to Franz that splitting this into two options is better.
>
> The state of extendedView is a module menu setting and as such saved in
> the user's uc. Changing the default state of extendedView with your
> patch will only affect new users, who never opened the list module
> before. This is redundant, as it's already possible to enable the
> extended view by default for new users, using this in localconf.php
> (maybe not widely known):
>
> $TYPO3_CONF_VARS['BE']['defaultUC'] = array (
> 'moduleData' => array (
> 'web_list' => array (
> 'bigControlPanel' => '1',
> ),
> ),
> );
>
> It's a standard support question to a client if he enabled exended view
> and I would like to get rid of this question, especially for upgraded
> installations.
>
> So I would like to have a TS option that always enables / disables
> extended view regardless of the already existing user's module setting.
> Attached solution comes with a new pageTSconfig called
> mod.web_list.extendedView.forceEnabled. If this is set, the user is
> unable to enable / disable extendedView.
> The checkbox doesn't make sense then, so it can be disabled with
> mod.web_list.extendedView.hideCheckbox=1.
>
>
> Why all this fuss? Consider the following situations:
> ...
> In both cases he is sure that extended view is always enabled and the
> checkbox is gone. It's even possible to disable the extended view again
> for some subpages or groups for whatever reason.
>
> So we have:
> - No default change when upgrading if admin doesn't care
> - New config mod.web_list.extendedView.hideCheckbox
> - New config mod.web_list.extendedView.forceEnabled

I think that is a great solution which covers all cases!

+1 on that.

Any chance this will go to alpha2 already?

Jörg