This repository has been archived by the owner on Dec 4, 2018. It is now read-only.
[FEATURE] Extend Wizard groups instead of replacing #305
Conversation
This file contains 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
So far, if you tried to put fluidcontent elements into an existing new content wizard group like "common", "special", etc it simply replaced all existing content elements and the title as well. This commit changes that behavior to extend existing groups instead, use the default core group translation, or use a localized translation for the group name.
mneuhaus
force-pushed
the
feature/extend_wizard_groups
branch
from
0cbb475
to
b493962
Compare
jmverges
added a commit
that referenced
this pull request
Nov 6, 2015
[FEATURE] Extend Wizard groups instead of replacing
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
So far, if you tried to put fluidcontent elements into an existing new content wizard group like
"common", "special", etc it simply replaced all existing content elements and the title as well.
This commit changes that behavior to extend existing groups instead, use the default core
group translation, or use a localized translation for the group name.
Example
This example puts a new content element inside the core wizard group "common", by default the
regular title from TYPO3 core will be used to render the Tab title
Translation
(Language/Locallang.xlf)If you specify a translation like this for your tab title that will be used instead