[TYPO3-core] RFC #16643: New sysext modules are placed incorrectly in the Web> module menu

Ernesto Baschny [cron IT] ernst at cron-it.de
Thu Dec 2 01:37:00 CET 2010


Hi,

there are some other caveats about this new possibility of uninstalling
sysext which used to be "hardcoded": Other extensions might want to
place their module "after:info" or "before:perm", and those might not
even be installed.

I suggest to later have some kind of "mapping" in the
t3lib_extMgm::addModule which will handle those edge cases gracefully so
that the user experience when upgraded don't get distorted.

So this is a story for "beta3", but for tonight I prefer not to continue
with more APIs, but get the beast out. :)

Cheers,
Ernesto

Ernesto Baschny [cron IT] schrieb am 02.12.2010 01:21:

> This is a SVN patch request.
> 
> Type: Cleanup
> 
> BT reference: http://bugs.typo3.org/view.php?id=16643
> 
> Branches: trunk
> 
> Problem:
> Since #15794 the old "hardcoded" sysext's list, perm, func and info lost
> their "fixed place" in the Web> modules menu. They now rely (like any
> other extension) in t3lib_extMgm::addModule().
> 
> Since they have after:layout in its calling, they were positioned after
> the "Web>Page" module. But since all had this property, they got added
> in the opposite order as intended (last one is in first position).
> 
> We still don't have any other way to position modules besides "after"
> and "before", which is not flexible enough. Until we have a solution, I
> remove the hardcoded "after:layout" so that they get added in the order
> of loading (in extList). In the dummy + intro package I will order them
> correctly so that they appear after Page.
> 
> Your ordering might vary depending on when you installed those extensions.
> 
> Cheers,
> Ernesto
> 
> 
> 
> 
> 
> 



More information about the TYPO3-team-core mailing list