[TYPO3-v4] Postponing 4.5 RC1

[Ernesto Baschny [cron IT]]

Hi Francois,

thanks for spotting that and also thanks for "helping out" in this last
important phase. The installation of extensions is also done using the
API by the introduction package. We changed it there for similar
reasons, here is the required code snippet:

	// Create an instance of language. Needed in order to make the em_index
work
$GLOBALS['LANG'] = t3lib_div::makeInstance('language');
$GLOBALS['LANG']->csConvObj = t3lib_div::makeInstance('t3lib_cs');
$this->em = t3lib_div::makeInstance('tx_em_Connection_ExtDirectServer');
$this->em->extensionList = t3lib_div::makeInstance('tx_em_Extensions_List');
$this->em->extensionDetails =
t3lib_div::makeInstance('tx_em_Extensions_Details');
$this->em->enableExtension($extensionKey);

The intro-package also does that during the installation process (which
is why we need to manually create the LANG object), but it works.

Could you check out if it works for that particular routine?

Thanks!

Cheers,
Ernesto

François Suter schrieb am 18.01.2011 15:12:
> Hi,
> 
>> - finish up all required upgrade wizards and have them tested (i.e.
>> workspaces)
> 
> I just stumbled on an issue related to that. I reported it here:
> 
> http://bugs.typo3.org/view.php?id=17114
> 
> IMO this is an absolute show stopper as it will lead to broken TYPO3
> installations. Repeating what I said in the core list (in a thread about
> the workspace upgrade wizard):
> 
> <quote>
> The method that adds extensions in the Install Tool is apparently very
> old and doesn't respect some features of the EM. Case in point when
> "extbase" is installed normally (via the EM), it is installed in both
> extList and extList_FE. It it also added first, because it has priority
> "top". The Install Tool adds it only to extList and adds it last. So if
> "extbase" is installed via this wizard, the user will end up with a
> broken configuration.
> 
> I have reported this in a separate report:
> http://bugs.typo3.org/view.php?id=17114
> 
> I've tried coming up with a patch, but it's very difficult because,
> partly because extension installation is not a simple process. It would
> be great if the EM could be called on, but this fails because it
> requires a "lang" object which we don't have in the BE. OTOH the process
> could be simplified in the Install Tool (for example because we know we
> are installing on sysexts), but I still couldn't come up with something
> quickly and didn't have time to dig further.
> </quote>
> 
> Cheers
>