[BUGFIX] Make extensions installable in classic installations #493
Conversation
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
Currently a site package as generated by this generator cannot be installed with the extension manager in a classic installation: https://forge.typo3.org/issues/106671 This is due to the fact that the Extension Manager expects a name scheme of the zip file like <extension_name>_<version>.zip This PR adjusts the name schmeme of the generated zip to be compatible with the needs of the Extension manger
sfroemkenjw
approved these changes
May 19, 2025
Contributor
Author
|
@andreaskienast this is already reviewed, could you merge and deploy please? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Currently a site package as generated by this generator cannot be installed with the extension manager in a classic installation:
https://forge.typo3.org/issues/106671
This is due to the fact that the Extension Manager expects a name scheme of the zip file like
<extension_name>_<version>.zipThis PR adjusts the name schmeme of the generated zip to be compatible with the needs of the Extension manger