[TYPO3-core] Merge module 'configuration' with 'reports' ?

[Felix Kopp]

+1 for the merge.

The editing options within Configuration are in my opinion not relevant 
any more nowadays. On the one hand editing system configuration is not 
easily possible. Also in many projects these changes must be versioned 
(git, svn) and thus being put in very specific files, which 
Configuration can not perform.

I am for the move and would plead to remove editing functionality to (a) 
become a Report and (b) don't mislead users.

This also migrates the Configuration to extbase, which is a nice plus.

Best,
Felix*


On 19.06.12 01:14, Christian Kuhn wrote:
> Hey there,
>
> Jigal recently did a nifty patch [1] to check for 'old' XCLASS
> registrations (those in $GLOBALS['TYPO3_CONF_VARS']['XCLASS'] that are
> deprecated with 6.0) in the reports module.
>
> Next, he pushed a patch [2] to the configuration module (main module
> item that shows content of $GLOBALS arrays) to also show all xclasses
> registered the 'new' way (via an ext_autoload entry).
>
> The problem is, that the configuration module does not really fit: It is
> constructed to show content of global arrays, but not to show
> configuration things that are located elsewhere.
>
> Thus, I proposed to add a new submodule to the reports module to show
> the registered xclasses. Currently, the reports module comes with a
> 'Status report' and a 'Installed Services' tab. It seems logical to me,
> to add a 'Registered XCLASS' tab there.
>
> And if we do this, the next step is to move the 'Configuration' module
> to a reports tab called 'global variable status' or something like that.
> This would reduce the main module by one entry and centralize all
> 'reporting and system analysis'. What do you think?
>
>
> Regards
> Christian
>
>
> [1] https://review.typo3.org/#/c/12140/
> [2] https://review.typo3.org/#/c/12155/