[TYPO3-v4] Interface for Install Tool Checks

Steffen Kamper info at sk-typo3.de
Sun Nov 7 14:17:04 CET 2010


Hey Benni,

Benjamin Mack schrieb:
> Hey all,
> 
> I'm currently working on a small thing, that is: a check to see if a
> TYPO3 installation is currently using the right character-set conversion
> tools (iconv, mbstring) or still using the homebrew code which is up to
> twice as slow. Well, while I was at it, I thought it'd be nice to have
> this check in the 1-2-3 installer automatically as well, not just in the
> update wizard. So I wanted to put it in a separate class. So I put
> everything in "tx_install_check_charactersettools"
> 
> Then I thought of a more general approach: An idea I had for quite some
> time was to have a proper check class for each of these things, so it's
> easy to add more, and a common thing to check in a TYPO3 extension e.g.
> if curl is used...
> 
> Right now we checks:
>  - in the installer (Basic Configuration, 1-2-3)
>  - in the reports module
>  - in the introduction package
>  - in various other places throughout the core.
> 
> So, I'd love to have a common interface / abstract class to define these
> checks.
>

+1 to centralize. Isn't this a good chance to place such checks in 
t3lib_div_utility_environment or simular?

> There are different kinds of checks:
> 
> Example 1)
>  - The php-version is below 5.2.0, TYPO3 shouldn't be installed, and
> should not be executed at all
> 
> Example 2)
>  - Memory Limit: If your memory limit is 16MB, you should still be able
> to install TYPO3, but it's not a perfect setup. Just a warning is
> produced, maybe a check if you can set it to 32MB through ini_set().
> 
> Example 3)
>  - No option for the csConv_utils method has been set yet. A message
> should be produced that you can upgrade to "mbstring" or whatever was
> found on the system. In the 1-2-3, this check should automatically
> choose the best option and set it in the localconf.php.
> 
>  => Same goes for ImageMagick :)
> 
> This way, all the specific code for these checks can be put in their own
> classes.
> 

or in one specific. You can split if you think it makes sense, but i 
also see them all related in a way.

Looking forward to your suggestion ;)

vg Steffen


More information about the TYPO3-project-v4 mailing list