[TYPO3-core] RFC #11474: Store separate extlist for the frontend

Michael Stucki michael at typo3.org
Tue Aug 11 17:54:55 CEST 2009


I have a few notes on this:

First, and most important: It is not acceptable to commit such changes
without documenting them accordingly. You promised to update NEWS.txt
and also the Core API, but both are still missing. In future, DO NOT
commit any code unless the documentation has been sent.

If there is no documentation until end of this week, I'm going to revert
this change therefore.

2. Can we please get rid of this notation:

| if (!($extLoadInContext = $TYPO3_CONF_VARS['EXT']['extList_FE'])) {

Instead, please write it this way:

| $extLoadInContext = $TYPO3_CONF_VARS['EXT']['extList_FE'];
| if (!$extLoadInContext) {

It is my personal preference, but I think everyone agrees that this
looks much better (and IDEs like it more anyway).

3. Please stick to the CGL when working on TYPO3core.

Attached is a patch which fixes 2) and 3). It is FYI24.

- michael

Rupert Germann schrieb:
> FYI committed to trunk
> 11474    rev 5765
> 11475    rev 5766
> 
> I'll write a note for this feature to NEWS.txt later today.
> 
> Currently it is required to trigger the generation of the new extlistFE
> by activating/de-activating an extension in EM.
> It was mentioned to add the extlistFE generation to the updater.
> This is not needed because the updater has already an option called
> "install sysexts" which will change the extlist anyway.
> 
> greets
> rupert
> 
> Rupert Germann schrieb:
>> Hi,
>>
>> this is a SVN patch request.
>>
>> Type: new feature / performance improvement
>>
>> Bugtracker references:
>> http://bugs.typo3.org/view.php?id=11474
>>
>> Branches: Trunk
>>
>> Problem:
>> If you have a lot of extensions loaded your frontend and backend becomes
>> slower and slower.
>>
>> Solution:
>> In order to at least reduce the load a bit we introduce a new
>> parameter to
>> the EM_CONF called "doNotLoadInFE".
>> If set to "1" this extension will not be included in the extlist to be
>> loaded in the frontend.
>> This also affects the temp_cached_* files in typo3conf which will also be
>> newly created.
>> there's a followup patch which sets "doNotLoadInFE" in some system
>> extensions which are not needed in FE:
>> http://bugs.typo3.org/view.php?id=11475
>>
>>
>> info / how to test:
>> apply both patches to your source.
>> To make the extmanager write the new var $TYPO3_CONF_VARS['EXT'
>> ['extList_FE'] to localconf.php disable and re-enable an extension.
>>
>> if someone has an idea how to make this automagically - let me know.
>>
>>
>> greets
>> rupert
>>
>> "There shall be no new TYPO3 version delivering content slower than its
>> predecessor!"
>>
>>
>>
>>


-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/


More information about the TYPO3-team-core mailing list