Bug #49782
closed
Extension Manager doesn't filter incompatible TYPO3 6.x Extensions!
0%
Description
The Extension-Manager for f.e. TYPO3 4.7 doesn't filter out TYPO3 Extensions targeting TYPO3 6.x.
There are a lot of Users and Existing Webpages basing on TYPO3 4.7 where a quick update to TYPO3 6.x may be impossible yet.
So it is very irritating that there are Updates announced for some Extensions that are incompatible.
In worst case one may install the wrong extension in a running TYPO3-Instance and break the whole page.
The "Old" Extension-Manager should:
- not announce Updates for Extension-Versions targeting TYPO3 6.x
- not allow installing the wrong version (default selected = current/latest)
Files
Updated by Gabriel Kaufmann / Typoworx NewMedia over 11 years ago
Note: Screenshot is just example. The "gridelements" vs "templavoila" note in the screenshot is not part of this issue.
Updated by Markus Klein over 11 years ago
- Status changed from New to Rejected
Hi Gabriel,
we are aware of this issue, but unfortunately this is not an Extension Manager problem, but a TER problem.
More precisely a missing feature for the TER. Currently, we don't have any information stored, which tells us, which extension version is compatible with which TYPO3 CMS version.
There is an option in ext_emconf.php to set the version compatibility of the extension, but this does not help for those situations, where you've different extension version for different TYPO3 CMS versions.
The only "solution" currently would be to register a new extension key and deploy the extension versions separately.
Regards
Markus
Updated by Gabriel Kaufmann / Typoworx NewMedia over 11 years ago
Hello,
thanks for the update.
Where can this bug for the TER be reported? It shouldn't be that hard to make the TER write typo3-version flag into it's Data-Feed imported by Extension-Manager to render a proper version-list in the Extension-Manager where you can select the Extension-Version or where the EM selects the "default-version" (=latest) to be installed.
Even if the issue is relocated to TER I don't think this can be a end-of-life solution.
In my opinion there still may leave about 1 year until TYPO3 6.x is stable and reliable enough (proper extension availability), until this can become a real replacement for old TYPO3-versions.
So this is no solution to deligate the problem back to the users.
Even if the TER needs some tuning to support the pre-availability of the TYPO3-version with the Extension-Version, the Extension Manager itself still needs an update to support the new Flag then.
Updated by Jigal van Hemert about 11 years ago
- Status changed from Rejected to Closed
Closed, because the Extension Coordination Team is working on this. Unfortunately adding features to TER does not go as fast as we wanted.
The first step (for which the patch may or may not be implemented on typo3.org at this moment) is to make the dependency on a TYPO3 version in each uploaded extension mandatory.
The rest of the steps can be found here: http://forge.typo3.org/projects/team-ect/wiki/TER_Clean-up
Once the TER has enough information to do some filtering it will be implemented in the Extension Manager.