Open
Conversation
The used Class is an internal API and should not be used. Problems occured during usage of ExtBase while retrieving TER informations of an extension without an existing TSFE.
Contributor
Author
|
Hi @schams-net , I think you already ported this to main branch. Could you publish a corresponding release? Or do you want to other issues to be refactored (beside doc ;-)) |
Owner
|
Merged into Version 5.x (for TYPO3 v13 LTS) hasn't been released yet. Do you need a back-port of the patch to version 4.x? |
Contributor
Author
|
Hi @schams-net , Do you need some hands for TYPO3 13 version? |
Owner
|
Thanks, @mgerdes-atl. Testing and feedback is always welcome 🙂 New version 5.0.0 released at: Many thanks for your code contribution for this release 🏅 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @schams-net ,
I removed the not official API part
TYPO3\CMS\Extensionmanager\Utility\ListUtilityinExtensionDetailsclass and substituted withPackageManager.Not sure about the conditions to check the extension. Currently we will only check for type
typo3-cms-*packages but nottypo3-cms-framework. Maybe we could remove theisValidExtensionKey()call.I did a short test on TYPO3 v12 and v13 which seems to be ok. Maybe you can include the changes an release a 4.X and 5.X Version.
We have main working in a v13 TYPO3 installation except the issue-42 reported by Daniel
Let me know if we could assist.