Project

General

Profile

Actions

Bug #38229

closed

Wrong Importpath After Adding 2nd Repository

Added by Medienfabrik Development over 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Extension Manager
Target version:
Start date:
2012-06-20
Due date:
% Done:

0%

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

Description

In the Extension Manager we added another (our own) repository.
Now, if you try to import an extension out of this repository or out of any other the generated link is wrong. It doesn't contain the domain and the path.

Error: The data transfer did not succeed. The T3X file "http://m/f/mf_myext_1.1.28.t3x" could not be fetched. Possible reasons: network problems, allow_url_fopen is off, cURL is not enabled in Install Tool.

Error: The data transfer did not succeed. The T3X file "http://t/t/tt_news_3.1.0.t3x" could not be fetched. (...)

If we delete the second repository everything works fine again.

We could trace the problem to the function getMirrorURL() in typo3_src/typo3/sysext/em/classes/index.php
The array $this->MOD_SETTINGS['extMirrors'] seems to be incorrect filled. It partially contains infos about repository 1 and repository 2.
Perhaps this could be the problem.

We reproduced the problem in Typo3 4.5.16, 4.6.7 and even in 4.6.9

Actions #1

Updated by Helmut Hummel over 12 years ago

  • Project changed from 336 to TYPO3 Core
Actions #2

Updated by Helmut Hummel over 12 years ago

  • Category set to Extension Manager
  • Target version set to 4.7.2
  • TYPO3 Version set to 4.5

Moved to the core project as this is no TER issue but a bug in the extension manager

Actions #3

Updated by Alexander Jahn over 12 years ago

Seems to be related to the bug here: http://forge.typo3.org/issues/33896

Actions #4

Updated by Wouter Wolters over 11 years ago

  • Status changed from New to Closed

Private repositories never have worked correctly with the new EM in 4.5. There was a patch that solved the problem (patch was by me) but it is hard to tackle this and we agreed to not invest more type in to this but rather use that time for the new EM since 6.0.

Actions

Also available in: Atom PDF