[TYPO3-core] RFC #16495: bug: conf.php files aren't corrected when installing extensions

Steffen Kamper info at sk-typo3.de
Tue Nov 23 01:56:38 CET 2010


Hi,

Ernesto Baschny [cron IT] schrieb:
> Jigal van Hemert schrieb am 22.11.2010 20:07:
>> Hi,
>>
>> Committed v2 to trunk in rev 9502.
> 
> Thanks for fixing, but after this change, the Intro Package stopped
> working (again). The IP uses the ExtDirect EM API to install and enable
> extensions. See:
> 
> 	typo3conf/ext/introduction/Classes/Import/Extension.php
> 
> See the constructor (where $this->em is created) and importExtension and
> enableExtension methods. There is no "$parentObject" which holds the
> information about the paths, so this fails. This is pretty ugly
> intra-dependency in some "parentObject" anyway.
> 
> Could someone please consider either "fixing" that in the Intro Package
> (as shipped in beta1) or provide some more easy to use API in the EM?
> 
> Doing that cleanup we should also get rid of the requirement of the
> calling class to create objects "extensionList" and "extensionDetails"
> from the outside. The API should create the objects when they need them!
> 


i already fixed that in the night of release. The type paths are static 
now to stop this dependency

tx_em_Tools::typePath($type)

will fix that again ...

vg Steffen


More information about the TYPO3-team-core mailing list