Be.container ViewHelper <f:be.container>

Migration

When this ViewHelper is used to register additional backend module resources like CSS or JavaScript, Be.pageRenderer ViewHelper <f:be.pageRenderer> can be used as drop-in replacement.

If the ViewHelper is used to additionally render an empty ModuleTemplate, this part should be moved to a controller instead. Simple example:

$moduleTemplate->setContent($view->render());
return new HtmlResponse($moduleTemplate->renderContent());

Examples

Simple:

<f:be.container>your module content</f:be.container>

"your module content" wrapped with proper head & body tags. Default backend CSS styles and JavaScript will be included.

All options:

<f:be.container pageTitle="foo"
    includeCssFiles="{0: '{f:uri.resource(path:\'Css/Styles.css\')}'}"
    includeJsFiles="{0: '{f:uri.resource(path:\'JavaScript/Library1.js\')}', 1: '{f:uri.resource(path:\'JavaScript/Library2.js\')}'}"
    addJsInlineLabels="{0: 'label1', 1: 'label2'}"
>
    your module content
</f:be.container>

"your module content" wrapped with proper head & body tags. Custom CSS file EXT:your_extension/Resources/Public/Css/styles.css and JavaScript files EXT:your_extension/Resources/Public/JavaScript/Library1.js and EXT:your_extension/Resources/Public/JavaScript/Library2.js will be loaded, plus some inline labels for usage in JS code.

Source code

Go to the source code of this ViewHelper: ContainerViewHelper.php (GitHub).

Arguments

The following arguments are available for <f:be.container>: