Bug #24785
closed
Install Extensions Globally from TER no more possible
0%
Description
Hi It seems to be no more possible to upload Extensions into the Global Extension Directory like it was possible with the former EM. When you click on the Name those Tabs are opening but no form to choose the install destination like before. This is not very useful to have to move global extensions one by one from folder to folder externally!
(issue imported from #M17283)
Files
Updated by Clemens Riccabona over 13 years ago
Hmm, with TYPO3 4.5.2 I can install extensions globally from TER if global install location is available.
BUT: updating global extensions does not work as expected. (the update does a lokal installation of lateste version). not very useful IMO.
Updated by Patrick Rodacker over 13 years ago
- File ext_global_install.png ext_global_install.png added
- Target version deleted (
0)
@Andreas Otto †: the functionality is there within the new em. Just right-click on the highlighted row an you will get a single-item-context-menu. Click the link an you will be presented with a popup where you can choose where to import the extension. IMO we should add the same functionality to the import icon on the left.
Updated by Alexander Opitz over 10 years ago
- Description updated (diff)
- Status changed from New to Needs Feedback
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5.35 or 6.2.4)?
Updated by Clemens Riccabona over 10 years ago
Hi there,
It sounds ridiculous, but yes, the problem seems to be persistent in some way:
1. It works flawlessly in the good "old" EM (old old old) in TYPO3 4.5, which caused me to never try the new one again on 4.5 installations since 4.5.0 or so .... ;)
2. I actually tested it in the new (new new new) EM in 6.2.4, -> no way to install extensions globally, if only the global location is set in InstallTool, EM just says: 'local is not in allowed paths' and runs into a popup-loop always stating that local is not in the allowed paths, what - damn'it - was set intentionally. ...
3. I actually tested it on 4.5.35 with the 'new' EM, and the way Patrick proposed 3 years ago works for me.
greets from tyrol,
Clemens
Updated by Clemens Riccabona over 10 years ago
And wow! The new (old old new) EM on 4.5.35 is really great in some kinds: the part with the fileviewer ist impressively developer-friendly!
so sad, that the all new EM is so - hmm - reduced, to say it friendly .... :O
Updated by Alexander Opitz over 10 years ago
- Category set to Extension Manager
- Status changed from Needs Feedback to New
So, the new EM which can be found in 6.2 can't install/update in global via TER.
For missing features please open a new issue (if not already present).
Updated by Clemens Riccabona over 10 years ago
... missing feature ...
it is a gone feature! gone features are missing as well, that's semantically correct. ...
Updated by Clemens Riccabona over 9 years ago
- Target version set to next-patchlevel
Is there any chance for getting a working solution right with current LTS?
Version 6.2.12 time writing continues denying global installation with all its sideeffects, as follows.
In detail:
it refuses to install extensions globally, and therefore it also does not update global extensions, it just downloads to local.
The last causes that malicious code of an outdated extensions just remains on server in global installation folder silently.
Silently because you have no information about installation places (local, global, system, combination of these because of duplication) in EM right now.
That again causes the problem, if you want to make something like a spring-cleanup of extensions,
you don't have a chance to see which extensions are sysext, which global-ext, which local-ext. Anoying.
Additionally there is no way to get grouping by extension-categories (some of the categories we had were bad, but it is not the right way to just remove a feature without replacement only because it was not perfect. This is NOT meant with 'enhancement').
Summa summarum: the whole thing (EM) remains just unusable, and I do not remember the last time I had to edit localconf.php (and its new, shiny replacements) by hand that often, and moving extension-folders manually and sort of things, all over since hmmm, let me think, 3.5 or 3.6, back in 2003...
Updated by Mathias Schreiber about 9 years ago
- Target version deleted (
next-patchlevel)
Updated by Christian Kuhn over 7 years ago
- Status changed from New to Closed
the 'global' feature will not be re-implemented.
Updated by Clemens Riccabona over 7 years ago
Christian Kuhn wrote:
the 'global' feature will not be re-implemented.
GREAT!
</sarcasm>