[Typo3-dev] phpmyadmin wants to be installed in GLOBAL

[Stephane Schitter]

Hello,

Looking at the code, the only reason it is locked as global is because the
TYPO3_MOD_PATH is not left to be managed by the extension manager, but is
somewhat hardcoded in conf.php and seems tricky to make more generic.

I was just concerned that it phpmyadmin is not part of system extensions, users
may wonder why it needs a global install, and as default settings prevent
extensions to be installed in global it would generate a few questions I can
predict.

I would be happy to make it more flexible, but with the current way
TYPO3_MOD_PATH is set from the extension manager (em), it would be a dirty
workaround.

Where is Typo3 going in terms of extensions locations handling code ? Should we
try make the TYPO3_MOD_PATH (and BACK_PATH) detection/handling more flexible
for such cases ?

Stephane


Selon Kasper Skårhøj <kasper2004 at typo3.com>:

> I can't remember taht of course, but the lock-flag is usually a good
> indication that there IS such a reason if you dig for it.
>
> - kasper
>
>
> On Sun, 2004-11-21 at 01:51, Stephane Schitter wrote:
> > Hello,
> >
> > Using the new CVS version, with the new list of sysext and no global exts,
> the
> > phpmyadmin extension seems to want only be installed in the global
> extensions
> > scope.
> >
> > Is there any good reason for phpmyadmin not wanting to install on local
> > extensions ?  (apart from the lock flag being in there...)
> >
> > Regards,
> > Stephane
> >