[TYPO3-core] RFC #9981: Bug: EM does not test for usage of mod.php-API and spuriously displays an error

Steffen Gebert steffen at steffen-gebert.de
Mon Nov 23 23:44:43 CET 2009


Am 22.11.2009, 15:37 Uhr, schrieb Andreas Kundoch  
<Andreas.Kundoch at mehrwert.de>:

> Problem:
> If an extension uses the new module API (as described in
> http://bugs.typo3.org/view.php?id=5278 and implemented) an error is
> displayed on import of an extension since TYPO3_MOD_PATH and BACK_PATH
> are not in the conf.php file but the EM tries to update them and fails.
>
> Solution:
> The patch extends the method writeTYPO3_MOD_PATH() to also test for a
> line matching $MCONF['script'] = '_DISPATCH'; If this applies, a simple
> notice is given instead of an error.
>
> Notes:
> Should also go in TYPO3_4-2 but code is different there, i'll see if I
> can provide another patch for that branch.

Thanks for taking care, Andreas!

Attached a v2, which adds some CGL.

To be honest, I don't like to notice, as "Extension installation" should  
already be enough information.
But as empty return would add an empty line:

+1 by reading and testing

Can be tested with phpmyadmin for instance.

Steffen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 9981_v2.patch
Type: text/x-diff
Size: 2791 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20091123/3a4d6578/attachment.patch>


More information about the TYPO3-team-core mailing list