Project

General

Profile

Actions

Feature #46197

closed

Add manual way to upload extension-lists etc.

Added by Stefan Neufeind over 11 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2013-03-12
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Some systems might not be able or allowed to access the internet directly. It might be handy to be able to switch on some "manual" mode in EM where to update the extension-list you get a URL to fetch an extension-list from, upload it "by hand" into EM and upon extension-updates also use this manual way.

I know this is not what it's "planned" to be like - but sometimes you can't have direct Internet-access for a TYPO3-installation.

Actions #1

Updated by Oliver Hader over 11 years ago

  • Target version set to 2222
Actions #2

Updated by Oliver Hader over 11 years ago

  • Project changed from 2269 to TYPO3 Core
Actions #3

Updated by Oliver Hader over 11 years ago

  • Category set to Extension Manager
Actions #4

Updated by Oliver Hader over 11 years ago

  • Target version deleted (2222)
Actions #5

Updated by Georg Ringer over 11 years ago

do we really need this? if the server is that strict, you probably should also use a deployment script and you won't install there extensions directly from ter anyway ...

Actions #6

Updated by Ingo Renner over 11 years ago

I agree with Georg, this sounds scary and a very rare case.

Actions #7

Updated by Alexander Opitz over 11 years ago

Following Scenario could be in my mind:

- Update Extension List via file to get Caretaker reporting installations that need an update.

But then you can update the database table "tx_extensionmanager_domain_model_extension" and the extensions via a deployment script.

Actions #8

Updated by Stefan Neufeind over 11 years ago

That's why I thought about a possibility to load the extensions.xml.gz manually and upload it via BE. Or maybe just have some job upload the file as "extensions__to_be_imported.xml.gz" in the dir and upon next hit through the BE extmgr would import it and copy it over the regular extensions.xml.gz? The import to database itself etc. is already in place. If we exchange extensions.xml.gz manually on the server we'd just need a way to trigger the DB-update.

Actions #9

Updated by Felix Kopp over 11 years ago

  • Status changed from New to Rejected

There should be no possibility to access the list manually. Since the security team reviews extension there is a process to blacklist insecure code.

Actions

Also available in: Atom PDF