#110170Local extensions can not be installed in classic mode if not published to TER; published Extensions are forced to be installed from TER
Description
In current TYPO3 v14-dev local classic mode extensions can not be installed, when they are not released to TER:
.clipboard-202607081107-lfzgm.png
If they are released to TER, they are forcefully downloaded from TER and any local change is discarded (the extension is replaced with what is downloaded from TER)
This happens since the following patch
> 94661: [TASK] Identify remote packages by key, version and remote | https://review.typo3.org/c/Packages/TYPO3.CMS/+/94661
Reason is:
The if ($extension->remote !== '') { in https://review.typo3.org/c/Packages/TYPO3.CMS/+/94632/4/typo3/sysext/extensionmanager/Classes/Service/ExtensionManagementService.php is always true becase the remote property is initialized with a fallback to 'ter' in https://github.com/TYPO3/typo3/blob/636e18dfd44e934ed39489259c5dcba696f45fda/typo3/sysext/extensionmanager/Classes/Domain/Model/Extension.php#L147
Therefore any local extension is assumed to be remote, which is not correct and causes the mentioned issues.
Reviews 9
- main 94704[BUGFIX] Revert "[TASK] Identify remote packages by key, version and remote"
- 14.3 96713[BUGFIX] Revert "[TASK] Identify remote packages by key, version and remote"
- main 94961[TASK] Store remote extension list as JSON files
- main 94960[TASK] Identify remote packages by key, version and remote
- 14.3 95017[TASK] Identify remote packages by key, version and remote
- main 94958[TASK] Store remote extension list as JSON file
- 14.3 94942[BUGFIX] Avoid removed getter in dependency check
- main 94938[BUGFIX] Avoid removed getter in dependency check
- 14.3 94705[BUGFIX] Revert "[TASK] Identify remote packages by key, version and remote"
Related issues 2
Files 1
History 610
-
Benjamin Franzke changed Related to #110144 <span data-processor="relativetime" data-value="2026-07-08T09:10:46+00:00" > 07/08/26, 09:10 </span>
-
Benjamin Franzke changed status
NewAccepted Is Regression 1 <span data-processor="relativetime" data-value="2026-07-08T09:12:25+00:00" > 07/08/26, 09:12 </span> -
Gerrit Code Review pushed patch set 1 for main to change 94704 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-07-08T09:32:17+00:00" > 07/08/26, 09:32 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 94705 <span data-processor="relativetime" data-value="2026-07-08T09:33:04+00:00" > 07/08/26, 09:33 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 94704 <span data-processor="relativetime" data-value="2026-07-08T09:33:24+00:00" > 07/08/26, 09:33 </span>
-
Benjamin Franzke commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-07-08T16:25:10+00:00" > 07/08/26, 16:25 </span> -
Stefan Bürk changed Related to #110271 <span data-processor="relativetime" data-value="2026-07-23T10:59:59+00:00" > 07/23/26, 10:59 </span>
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-08-11T08:51:02+00:00" > 08/11/26, 08:51 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 96713 status
ClosedUnder Review <span data-processor="relativetime" data-value="2026-10-15T08:20:19+00:00" > 10/15/26, 08:20 </span> -
Benni Mack commented and changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2026-11-07T22:11:20+00:00" > 11/07/26, 22:11 </span>fixed in the meantime, but referenced wrong in gerrit, which is why this change re-opened.
Applied in changeset commit:63f64ae9fea0a1f2b89ab0aa549b9fa5366247e4.