-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CreateModuleWithExtbase.rst #5138
Conversation
Extend the code example how to create links to Extbase controller actions. It is not obvious based on the current documentation, that the array-key of the new module-configuration must be used, plus passing the controller and action name as arguments. The issue was solved in Slack (thanks Garvin!) and is now added here for future use.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would be fine by me! Lina, Stefan?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very Helpfull, thank you!
The backport to
stderr
stdout
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-13.4 13.4
# Navigate to the new working tree
cd .worktrees/backport-13.4
# Create a new branch
git switch --create backport-5138-to-13.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick f82b9209df1d3a2119d70867a4d41342897aec6a
# Push it to GitHub
git push --set-upstream origin backport-5138-to-13.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-13.4 Then, create a pull request where the |
Congratulations for your first contribution to this GitHub Organization! |
Extend the code example how to create links to Extbase controller actions. It is not obvious based on the current documentation, that the array-key of the new module-configuration must be used, plus passing the controller and action name as arguments. The issue was solved in Slack (thanks Garvin!) and is now added here for future use.
Extend the code example how to create links to Extbase controller actions. It is not obvious based on the current documentation, that the array-key of the new module-configuration must be used, plus passing the controller and action name as arguments. The issue was solved in Slack (thanks Garvin!) and is now added here for future use. Co-authored-by: Hanns <1685510+moongazer@users.noreply.github.com>
Extend the code example how to create links to Extbase controller actions. It is not obvious based on the current documentation, that the array-key of the new module-configuration must be used, plus passing the controller and action name as arguments. The issue was solved in Slack (thanks Garvin!) and is now added here for future use.
Extend the code example how to create links to Extbase controller actions. It is not obvious based on the current documentation, that the array-key of the new module-configuration must be used, plus passing the controller and action name as arguments. The issue was solved in Slack (thanks Garvin!) and is now added here for future use. Co-authored-by: Hanns <1685510+moongazer@users.noreply.github.com>
Extend the code example how to create links to Extbase controller actions in modules. It is not obvious based on the current documentation, that the array-key of the new module-configuration must be used, plus passing the controller and action name as arguments.
The issue was solved in Slack (thanks Garvin!) and is now added here for future use.