[BUGFIX] custom backend templates #577
Merged
+236
−111
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
bmack
approved these changes
Feb 13, 2025
the container grid is not longer rendered after the
content of the StandardContentRenderer but is assign
as a variable "tx_container_grid" to the record.
this variable is used in a backend template:
<f:format.raw>{tx_container_grid}</f:format.raw>
container shipped the default backend template (again, we has
dropped this in EXT:container 3.0)
in v12 and v13 the ContainerPreviewRenderer is no longer used
we use PageContentPreviewRendering Event Listener instead of
the ContainerPreviewRenderer
the Listener assigns the container grid to tx_container_grid
in v11 the PreviewRenderer is still used but assigns the
grid as a variable instead of rendering the grid after the content
background: in v13 the Event Listener "FluidBasedContentPreviewRenderer"
was introduced for rendering backend templates and "disables" StandardContentRenderer
if a backend template is defined.
in addition with this change you can also render custom stuff
in you backend template after the grid, which was not possible before
Fixes: #563
to not break the BeforeContainerPreviewIsRenderedEvent Method Signatures we put the GridColumnItem into the runtime cache in the ContainerPreviewRenderer renderPageModulePreviewHeader Method (which is always called) and fetch it in the GridRenderer to pass it tho the Event. This is a hack to not break the event, but fix the custom BackendTemplate usage (s. dfc61c4) Relates to: #563
achimfritz
force-pushed
the
bugfix/backend-template-2
branch
from
107c43e to
d0919f4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
the container grid is not longer rendered after the content of the StandardContentRenderer but is assign as a variable "tx_container_grid" to the record.
this variable is used in a backend template:
<f:format.raw>{tx_container_grid}</f:format.raw>container shipped the default backend template (again, we has dropped this in EXT:container 3.0)
in v12 and v13 the ContainerPreviewRenderer is no longer used we use PageContentPreviewRendering Event Listener instead of the ContainerPreviewRenderer
the Listener assigns the container grid to tx_container_grid
in v11 the PreviewRenderer is still used but assigns the grid as a variable instead of rendering the grid after the content
background: in v13 the Event Listener "FluidBasedContentPreviewRenderer" was introduced for rendering backend templates and "disables" StandardContentRenderer if a backend template is defined.
in addition with this change you can also render custom stuff in you backend template after the grid, which was not possible before
Fixes: #563