[TYPO3-dev] Cosmetics with localconf.php

[Ries van Twisk]

On Apr 29, 2010, at 3:41 PM, Steffen Kamper wrote:

> Hi,
>
> i discussed this issue with Christian Kuhn and Jeff Segars and we  
> are positive about it, but i like to hear your opinion.
>
> Install tool doesn't care about cosmetics in that file, it also adds  
> comments to it like
>
> // Updated by TYPO3 Install Tool ...
> EM does it too:
> // Updated by TYPO3 Extension Manager ...
>
> When ever you edit this file manually, and 100% of devs i know do  
> that, these lines are without a real effort and mostly disturb.
>
> So i would like to get rid of them.
>
> Further i would like to get the file sorted in sections like
>
> // DB params
> $typo_db_username = ..
> ...
>
> // System
> $TYPO3_CONF_VARS['SYS']...
> ...
>
> // Graphics
> $TYPO3_CONF_VARS['GFX']...
> ...
>
> // BE
> $TYPO3_CONF_VARS['BE']...
> ...
>
> // FE
> $TYPO3_CONF_VARS['FE']...
> ...
>
> // Extensions
> $TYPO3_CONF_VARS['EXT']
> ...
>
> This would make it more easy to change / read the file, port it to  
> another server, use it with svn etc.
>
> May be you'd say this is a feature, but as it doesn't change any  
> functionality i would declare it as clean-up.
>
> Your opinion or suggestion?
>
> vg Steffen
> _______________________________________________



Steffen,

I like the idea,
but I have come across several websites where items are added in the  
this file
that depend on it's position. For example I have seen an installation  
that did something
with the database because of load balancing purposes and 'things'  
needed to happen in a specific order (order is important here).
I have also seen some installation where additional files where  
included before or after some other file and config.

I wonder if the file get's sorted somehow, some installations might  
get messed up when the file
is 'migrated' to the sorted version.


Ries