[TYPO3-core] Question about new LocalConfiguration file and extension list

[Jigal van Hemert]

On 5-9-2012 9:28, Ernesto Baschny [cron IT] wrote:
> But then the "comma-separated-list" should be auto-magically created by
> the bootstrap code and not be present in the file that is "potentially"
> manually edited by an admin. I was also wondering several times why this
> is redundantly stored in this file and which one I should modify for it
> to work.

TYPO3\CMS\Core\Extension\ExtensionManager::writeNewExtensionList() 
writes the list to both the array and the comma separated list.

The array version has priority.
The list is there to prevent code to break if people don't use API methods.
Another use case is a TS condition which checks for a loaded extension.

>>> Does it mean that if you add an
>>> extension manually, or if you want to change the load order manually,
>>> you have to update both?
>>
>> Yes, but if you do that you are already doing eerie things anyway :-)
>
> I wonder why? Any other way to for example remove extensions that are
> giving "Fatal error" in the whole bootstrap mechanism because they are
> using obsolete methods in ext_localconf.php for example? This is what I
> constantly have the need to do while testing 6.0.. :(

Removing extensions manually is a different thing; it's an emergency 
situation and not a normal operation. Earlier you mentioned *adding* and 
extension (which should be done via the Extensions Manager module) and 
modifying the load order manually.
If you need an extension to load before a particular extension then this 
is obviously a missing feature. Maybe we should add it in future releases?

-- 
Jigal van Hemert
TYPO3 Core Team member

TYPO3 .... inspiring people to share!
Get involved: typo3.org