[TYPO3-core] RFC: Bug #17244: Error Message while Updating 4.4.6 > 4.5

[Oliver Hader]

Hi Steffen,

Am 28.01.11 16:31, schrieb Steffen Kamper:
> Hi,
> 
> Am 28.01.2011 14:09, schrieb François Suter:
>> Hi,
>>
>>> as the class tx_em_Connection_ExtDirectServer is nearly independent from
>>> loading status of em, wouldn't it be easier to just include it if not
>>> present?
>>
>> I would think not. Calling tx_em_Connection_ExtDirectServer is just the
>> start of the process. Quite a few other "em" classes are called after
>> that, aren't they? In this case it is better to build a dependency on
>> "em" rather than having duplicate code for installing extensions in the
>> Install Tool (as we had until now / still have, but could now be
>> deprecated).
>>
> 
> it's true that other classes are instanced as well. Though no class use
> t3lib_extMgm::extPath('em') (the api still does, but i will change that,
> and index.php which is not needed at all) the only thing is needed is
> the ext_autoload of em. So with using this one we are independent from
> em being installed.
> 
> @Ernesto - i don't think moving this to t3lib is a good idea. It's a
> specialized API which is only em and should resist in em.
> 
> I only would like not to overcomplicate the install process, so after my
> change in API i would simply add the ext_autoload, and all classes can
> be found.

Well, I don't think this makes things complicated. We just should ensure
that the install tool has the basic required extensions available if
they are required there. It's not required to load all EM classes by
default and create a new very special case there...

If there are doubts concerning the new "ignoredExt" settings, this could
be removed. Thus the install tool uses the extensions defined in the new
constant - otherwise in FE and BE the values as given in requiredExt are
used.

What do you think?

olly
-- 
Oliver Hader
TYPO3 v4 Core Team Leader

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