Project

General

Profile

Actions
Copy link

Bug #38847

closed

New Extension manager, malformed private TER url

Added by Anisur R. Mullick over 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Steffen Kamper
Category:
Extension Manager
Target version:
-
Start date:
2012-07-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
Sprint Focus:

Description

The extension manager of TYPO3 version 4.6.x and above cannot pull T3X files from private TER. The settings could be successfully carried out, and the extension list is fetched from private TER. But when one tries to install the extension, it gives network error saying either curl is not enabled or allow_url_fopen is disabled. The problem in actual is, the em cannot create proper url to the extension repository. It does not read the host and path from the mirror file of the private TER during importing.

Screen shots are uploaded to confirm that private TER is working correctly, as extensions can be installed in older TYPO3 versions (4.5.x, 4.4.x).

Files

Download all files
em_malform_url_private_ter_4.7.png (121 KB) em_malform_url_private_ter_4.7.png Anisur R. Mullick, 2012-07-10 13:06
em_list_extn_private_ter_4.7.png (110 KB) em_list_extn_private_ter_4.7.png Anisur R. Mullick, 2012-07-10 13:06
em_private_ter_settings_4.7.png (121 KB) em_private_ter_settings_4.7.png Anisur R. Mullick, 2012-07-10 13:06
em_import_success_private_ter_4.5.png (97 KB) em_import_success_private_ter_4.5.png Anisur R. Mullick, 2012-07-10 13:06
em_private_ter_settings_4.5.png (128 KB) em_private_ter_settings_4.5.png Anisur R. Mullick, 2012-07-10 13:06
Actions
Copy link
 #1

Updated by Alexander Jahn over 12 years ago

This might be related to the report here: http://forge.typo3.org/issues/33896

Actions
Copy link
 #2

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
Copy link

Also available in: Atom PDF