Extension Repository search not local but online
|Priority:||Should have||Due date:|
When I want to instal an extension, the Extension Repository must search online and not in the local MySQL table "cache_extensions".
I want to install extension CoolUri but it could not found local. So I click on the Retrieve/Update button on the Import Extension page. But after 60 seconds I get a time out message. So I must enlarge the PHP max execution time.
This is really frustrating. I don't want to enlarge the PHP max execution time and I don't want to import over 21.000 extensions in a MySQL table.
Please make it user friendly.
(issue imported from #M17579)
|related to Core - Bug #24507: TemplaVoila extension not visible in Extension manager||Resolved||2011-01-10|
Updated by Steffen Kamper over 2 years ago
with 4.5 this has been improved, max. memory usage is 12MB for fetching extensions.
Updated by Dmitry Dulepov over 2 years ago
If you can't give the system resources it needs, use another system. That's all. TYPO3 is enterprise level CMS and requires certain resources. This has nothing to do with being user friendly.
Updated by Sigfried Arnold over 2 years ago
@Dmitry your answer is a bit odd. It is true that TYPO3 is an enterprise CMS but this does not imply that it have to waste resources.
There is absolutely no use in fetching a huge list of extensions if you just want one single extension updated.
Currently i rather go to typo3.org/extensions/repository/ and check for the current version rather than using the update-feature in the backend - its faster and usually up to date. I bet many users do the same.
The EM should simply check for the current version of the extensions key entered in "Look up extensions" live in the TER.
- will produce less traffic (fetching the whole list will produce more traffic; navigating to typo3.org manually will produce more traffic too)
- much faster than retrieving a whole list
Just tested it: retrieving the current list (22386 records) took around 2.5 minutes. if you want to check for an update of a single extension you and go to typo3.org muliple times and download it.
And no - it had nothing to do with limited hardware resources, the hardware on that system on enterprise level.
How is this "enterprise" if you have to update over 22000 extensions (8.79 MB) to check if a single extension is up to date? That many overhead (both in time and amount of data) is ridiculous.