Skip to content

Added doc for additional parameter for ibexa_render #3043

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.

Sign up for GitHub

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

Open
mnocon wants to merge 8 commits into
base: 4.6
Choose a base branch
from
Open

Added doc for additional parameter for ibexa_render #3043

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
96d3331
Added doc for additional parameter for ibexa_render
mnocon Feb 4, 2026
8ceb8e4
Added update sections
mnocon Feb 5, 2026
7838c3f
Update docs/update_and_migration/from_5.0/update_from_5.0.md
mnocon Feb 5, 2026
ea219ed
Merge remote-tracking branch 'origin/4.6' into ibexa_render_parameters
mnocon Feb 11, 2026
e792889
Reworked RN drafts
mnocon Feb 11, 2026
5617cfa
Update docs/release_notes/ibexa_dxp_v4.6.md
mnocon Feb 17, 2026
d389e92
Removed RN entries
mnocon Mar 6, 2026
14bee25
Merge remote-tracking branch 'origin/4.6' into ibexa_render_parameters
mnocon Mar 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/templating/twig_function_reference/content_twig_functions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ You can provide `ibexa_render()` with either a content item or a Location object
|`content` or `location`|[`Content`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Content.html), [`ContentAwareInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-ContentAwareInterface.html) or [`Location`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Location.html)|Content item or its location.|
|`method`|`string`|(optional) [Rendering method](#rendering-methods). One of: `direct`, `inline`, `esi`, `ssi`. (Default method is `direct`)|
|`viewType`|`string`|(optional) [View type](template_configuration.md#view-types). (Default view type is `embed`)|
|`params`|`array`|(optional) Hash of variables to pass to the template.|

#### Rendering methods

Expand All @@ -48,6 +49,13 @@ You can pass one of the following rendering methods to `ibexa_render()`:
{{ ibexa_render(content, {'viewType': 'line'}) }}

{{ ibexa_render(content, {'method': 'inline'}) }}

{{ ibexa_render(content, {
'viewType': 'line',
'params': {
'custom_param': 'custom_value'
}
}) }}
Comment on lines +53 to +58
Copy link
Contributor

@adriendupuis adriendupuis Feb 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens for method: esi? One HTTP cache per custom_value I guess as it probably goes to the _fragment URL GET params. So this custom_value also need to be scalar. The best would be a link in the method raw of the table on esi to some ESI doc but there is no clearly dedicated page about that. Probably something to rework later, taking some ideas from the training.

Copy link
Contributor

@vidarl vidarl Feb 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

method: esi is also supported. And yes, that will end up as a value in the _hash GET parameter to the _fragment controller

```

## Content information
Expand Down