Wrong extension precedence in TYPO3 6.2
When an extension is installed locally in typo3conf/ext/ it should always take precedence over a system extension from typo3/sysext/.
This was the case in the last LTS and is still documented like that here:
However in 6.2.3 this is not the case. When I try to install t3skin locally and open the extension manager, it reverts to the system extension always.
I tracked this behaviour down to typo3/sysext/core/Classes/Package/PackageManager.php.
The reason are lines 85-90. Because they are used to iterate the extension paths, the typo3conf/ext/ path is found first and typo3/sysext/ last. When the found extension paths are traversed, naturally the latter overwrites the first, leaving the system extension active always. And since the extension manager aggressively tries to save the PackageStates (which is a good thing), the system extension is active again after I open the extension manager.
Patch will be attached.
Updated by Caspar Stuebs over 6 years ago
imo the extension precedence is independent from the other stuff. At this moment only the system extension is respected. If the order is changed, only the local extension is respected.
The question how to respect the same extension in different places are another bug and should go into another ticket.