Project

General

Profile

Actions
Copy link

Bug #59147

closed

Wrong extension precedence in TYPO3 6.2

Added by Nils Blattner over 10 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
7.3 (Packages)
Start date:
2014-05-27
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

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:
http://docs.typo3.org/TYPO3/CoreApiReference/ExtensionArchitecture/SystemGlobalAndLocalExtensions/Index.html

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.

Files

bug_59147.diff (1.02 KB) bug_59147.diff Nils Blattner, 2014-05-27 17:10

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Bug #55646: Framework Packages aren't sorted properly if package is overriten in typo3conf/extClosed2014-02-04

Actions
Precedes TYPO3 Core - Bug #59831: Package loading order is currupted by faulty patch #59147ClosedMarkus Klein2014-06-24

Actions
Actions
Copy link

Also available in: Atom PDF