Feature #46197
closed
Add manual way to upload extension-lists etc.
Added by Stefan Neufeind over 11 years ago.
Updated over 11 years ago.
Category:
Extension Manager
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.
- Target version set to 2222
- Project changed from 2269 to TYPO3 Core
- Category set to Extension Manager
- Target version deleted (
2222)
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 ...
I agree with Georg, this sounds scary and a very rare case.
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.
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.
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by