Netgen Content Browser Documentation¶

Netgen Content Browser is a Symfony bundle that provides an interface which selects items from any kind of backend and returns the IDs of selected items back to the calling code. Main use case is to provide a way to hook into a CMS backend and select items from the backend from apps built on top of that same CMS.

For example, Netgen Layouts uses Content Browser to select items which will be added to block collections.

Out of the box, Netgen Content Browser has the following plugins:

Selecting content and locations from eZ Platform CMS
Selecting tags from Netgen Tags Bundle for eZ Platform
Selecting products and taxons from Sylius eCommerce

Note

This documentation assumes you have a working knowledge of the Symfony Framework. If you’re not familiar with Symfony, please start with reading the Quick Tour from the Symfony documentation.

Reference¶

Installation instructions¶

Use Composer¶

Run the following command to install Netgen Content Browser:

$ composer require netgen/content-browser

Activate the bundle¶

Activate the Content Browser in your kernel class together will all other required bundles:

$bundles = array(
    ...

    new WhiteOctober\PagerfantaBundle\WhiteOctoberPagerfantaBundle(),
    new Sensio\Bundle\FrameworkExtraBundle\SensioFrameworkExtraBundle(),
    new Netgen\Bundle\CoreUIBundle\NetgenCoreUIBundle(),
    new Netgen\Bundle\ContentBrowserBundle\NetgenContentBrowserBundle(),
    new Netgen\Bundle\ContentBrowserUIBundle\NetgenContentBrowserUIBundle(),

    new AppBundle\AppBundle(),
);

Activate the routes¶

Add the following to your main routing.yml file to activate Content Browser routes:

netgen_content_browser:
    resource: "@NetgenContentBrowserBundle/Resources/config/routing.yml"
    prefix: "%netgen_content_browser.route_prefix%"

Install assets¶

Run the following from your repo root to install Content Browser assets:

$ php app/console assets:install --symlink --relative

Configuration reference¶

Configuration of Content Browser is done per item type.

To register the new item type in Content Browser, you need to add it to the list of item types in configuration:

netgen_content_browser:
    item_types:
        my_item_type:
            ...

The following lists all configuration options available in Netgen Content Browser for every item type:

Item type configuration¶

Configuration for each item type can be configured separately and can be accessed from Symfony DIC with the service name netgen_content_browser.config.<item_type> where <item_type> should be replaced with the actual identifier of your item type.

`name`¶

This is the human readable name of your item type. You can use a translation placeholder here, which will be translated with ngcb catalog.

type: string, required: Yes, example: item_types.my_item_type

`min_selected`¶

This is the number of items that needs to be selected at minimum to be able to close the selection dialog.

Set this to 0 to disable the limit. This configuration can be overriden when calling the dialog.

type: int, required: No, default: 1

`max_selected`¶

This is the number of items that needs to be selected at maximum to be able to close the selection dialog.

Set this to 0 to disable the limit. This configuration can be overriden when calling the dialog.

type: int, required: No, default: 0

`parameters`¶

With this, you can transfer a custom list of parameters to the item configuration, together with all other configuration values described in this document.

type: array, required: No, default: []

`tree`¶

enabled¶

Controls if the tree panel will be displayed or not.

This configuration can be overriden when calling the dialog.

type: bool, required: No, default: true

`search`¶

enabled¶

Controls if the search panel will be displayed or not.

This configuration can be overriden when calling the dialog.

type: bool, required: No, default: true

`preview`¶

enabled¶

Controls if the preview panel will be displayed or not.

This configuration can be overriden when calling the dialog.

type: bool, required: No, default: true

template¶

Specifies the template that will be used to render the preview panel.

type: string, required: Yes, example: @App/ngcb/my_item_type.html.twig

`columns`¶

Specifies the list of columns that are available for the item type.

At least a column with identifier name must exist and either template or value_provider configuration must be specified for each of the columns.

name¶

This is the human readable name of your column. You can use a translation placeholder here, which will be translated with ngcb catalog.

type: string, required: Yes, example: columns.my_item_type.some_column

template¶

Specifies the template that will be used to render the cell in the column.

type: string, required: No, example: @App/ngcb/my_item_type/some_column.html.twig

value_provider¶

Specifies the identifier of a value provider that will be used to provide the cell value.

type: string, required: No, example: my_item_type\some_column

`default_columns`¶

Specifies the list of columns that will be shown when the dialog is first opened.

type: array, required: Yes, example: ['name', 'other_column']

Full configuration example¶

The following code block shows the full configuration example of an item type with identifier my_item_type:

netgen_content_browser:
    item_types:
        my_item_type:
            name: item_types.my_item_type
            min_selected: 1
            max_selected: 0
            tree:
                enabled: true
            search:
                enabled: false
            preview:
                enabled: true
                template: '@App/ngcb/my_item_type.html.twig'
            columns:
                name:
                    name: columns.name
                    value_provider: name
                some_column:
                    name: columns.my_item_type.some_column
                    template: '@App/ngcb/my_item_type/some_column.html.twig'
                other_column:
                    name: columns.my_item_type.other_column
                    value_provider: my_item_type\other_column
            default_columns: [name, some_column]

Available Symfony services¶

A number of Symfony services is available for usage in your code:

`netgen_content_browser.registry.backend`¶

This service is a registry which holds all available backends. It is an implementation of Netgen\ContentBrowser\Registry\BackendRegistryInterface and you can use it to manually load Content Browser items by their ID.

$backendRegistry = $this->get('netgen_content_browser.registry.backend');
$eZLocationBackend = $backendRegistry->getBackend('ezlocation');

$item = $eZLocationBackend->loadItem(42);

Configuration services¶

Every backend has its own configuration service which can be used by the backend to access all config options specified in Symfony semantic config, as well as any custom parameters passed to the backend by the calling code. These services all implement Netgen\ContentBrowser\Config\ConfigurationInterface interface.

The names of these services are netgen_content_browser.config.ITEM_TYPE. So for ezlocation item type, service name would be netgen_content_browser.config.ezlocation.

Symfony dependency injection tags¶

The following lists all dependency injection tags and their usage available in Netgen Content Browser:

`netgen_content_browser.backend`¶

Purpose: Adds a new backend to the system

A backend is a service that provides methods to load the list of items and locations in Content Browser interface. A backend needs to implement Netgen\ContentBrowser\Backend\BackendInterface interface.

When registering a new backend, you need to use the item_type attribute in the tag to specify the item type the backend is used for:

app.content_browser.my_backend:
    class: AppBundle\ContentBrowser\MyBackend
    tags:
        - { name: netgen_content_browser.backend, item_type: my_backend }

`netgen_content_browser.column_value_provider`¶

Purpose: Adds a new column value provider for a single item column

A column value provider is a service that provides a value to a column displayed in Content Browser interface for a specific item. Column value provider needs to implement Netgen\ContentBrowser\Item\ColumnProvider\ColumnValueProviderInterface interface.

When registering a new column value provider, you need to use the identifier attribute in the tag to attach a unique identifier to the provider:

app.content_browser.my_item.custom_column:
    class: AppBundle\ContentBrowser\MyItem\CustomColumn
    tags:
        - { name: netgen_content_browser.column_value_provider, identifier: my_item\custom_column }

Upgrades¶

Upgrading from 0.7.0 to 0.8.0¶

Upgrade `composer.json`¶

In your composer.json file, upgrade the version of netgen/content-browser package to ~0.8.0 and run the composer update command.

Breaking changes¶

The following breaking changes were made in version 0.8 of Content Browser. Follow the instructions to upgrade your code to this newer version.

sections config has been removed from configuration of item types since overriding sections has never been properly implemented. Remove the section from your own item type definitions.

The concept of item serializer handlers is removed. Previously, they were used to specify how certain data will be serialized for an item. One method that the Netgen\ContentBrowser\Item\Serializer\ItemSerializerHandlerInterface provided has been moved to Netgen\ContentBrowser\Item\ItemInterface, so you need to move your implementation there:

// Before

<?php

namespace AppBundle\ContentBrowser\Item\Serializer\Handler;

use Netgen\ContentBrowser\Item\ItemInterface;
use Netgen\ContentBrowser\Item\Serializer\ItemSerializerHandlerInterface;

class MyItemSerializerHandler implements ItemSerializerHandlerInterface
{
    /**
     * Returns if the item is selectable.
     *
     * @param \Netgen\ContentBrowser\Item\ItemInterface $item
     *
     * @return bool
     */
    public function isSelectable(ItemInterface $item)
    {
        // Determine if the item is selectable
    }
}

// After

<?php

namespace AppBundle\ContentBrowser\Item\MyItem;

use Netgen\ContentBrowser\Item\ItemInterface;

class Item implements ItemInterface
{
    /**
     * Returns if the item is selectable.
     *
     * @return bool
     */
    public function isSelectable()
    {
        // Determine if the item is selectable
    }
}

The concept of item template value providers is removed. Previously, they were used to provide the variables that will be used by the templates to render the item preview and columns. Now, one single variable called item is injected to all Twig templates. This variable holds the actual item which is rendered, which means that your Netgen\ContentBrowser\Item\ItemInterface objects need to provide everything that will be used to render the templates.

// Before

<?php

namespace AppBundle\ContentBrowser\Item\Renderer\TemplateValueProvider;

use Netgen\ContentBrowser\Item\ItemInterface;
use Netgen\ContentBrowser\Item\Renderer\TemplateValueProviderInterface;

class MyItemTemplateValueProvider implements TemplateValueProviderInterface
{
    /**
     * Provides the values for template rendering.
     *
     * @param \Netgen\ContentBrowser\Item\ItemInterface $item
     *
     * @return array
     */
    public function getValues(ItemInterface $item)
    {
        $thingOne = ...;
        $thingTwo = ...;

        return array(
            'thingOne' => $thingOne,
            'thingTwo' => $thingTwo,
        );
    }
}

// After

<?php

namespace AppBundle\ContentBrowser\Item\MyItem;

use Netgen\ContentBrowser\Item\ItemInterface;

class Item implements ItemInterface
{
    /**
     * Returns thing one.
     *
     * @return mixed
     */
    public function getThingOne()
    {
        return ...;
    }

    /**
     * Returns thing two.
     *
     * @return mixed
     */
    public function getThingTwo()
    {
        return ...;
    }
}

In your templates, instead of directly using variables thingOne and thingTwo, you will now use item.thingOne and item.thingTwo.

Upgrading from 0.8.0 to 0.9.0¶

Upgrade `composer.json`¶

In your composer.json file, upgrade the version of netgen/content-browser package to ~0.9.0 and run the composer update command.

Breaking changes¶

The following breaking changes were made in version 0.9 of Content Browser. Follow the instructions to upgrade your code to this newer version.

Many services that should not be used directly and are not part of public API are now marked as private in service container. Remove usage of those services in your code. Note that some of the services (forms and event subscribers) were not marked as private due to incompatibilities with Symfony 2.8, but will be marked as such in a future update.
Most of the internal protected dependencies and methods were made private and classes made final. Rather than extending internal classes, you need to use other patterns when changing built in behaviour.
ezlocation and ezcontent backends have been merged to one backend that handles both eZ location and content items. This means that eZ location and eZ content specific items and column value providers have also been merged into one. You need to adapt your code that uses them to use the new backend, item and column value providers.

The cookbook¶

The cookbook provides a handful of recipes with which you can learn how to extend and use Netgen Content Browser.

The cookbook¶

The cookbook provides a handful of recipes with which you can learn how to extend and use Netgen Content Browser.

Implementing a custom backend¶

Implementing a custom backend is a way to add support for your CMS of choice to the content browser.

The concept of a backend revolves around the concept of locations and items. Locations are comparable to folders in a file system, while items are comparable to files. The location is used to build the tree structure that holds the items, and items are what is actually selectable in the content browser dialogue. Types of items are identified by their string identifier and every backend needs to work with and return only one item type.

When implementing a backend and all its required services, it is left up to you to define whether some locations can also be items, (like in eZ Platform, where all locations in a tree are selectable), or not (like in Sylius, where locations are built from Sylius taxons and are not selectable), or some other combination (like in Netgen Tags, where the root location is a virtual one and thus not selectable, while all other are).

Items need to implement Netgen\ContentBrowser\Item\ItemInterface while locations need to implement Netgen\ContentBrowser\Item\LocationInterface. When a location is also an item, it needs to implement both LocationInterface and ItemInterface.

Implementing a backend involves the following:

Configuring and enabling your new item type
Creating a Symfony service implementing Netgen\ContentBrowser\Backend\BackendInterface
Creating objects implementing ItemInterface and LocationInterface which will be returned by the methods from the backend service
Creating and configuring the templates used to render the columns or creating a Symfony service implementing Netgen\ContentBrowser\Item\ColumnProvider\ColumnValueProviderInterface for every column you add that’s not using a template for rendering

Configuring and enabling your new item type¶

Once you decide on your new item type identifier (in these examples, we will use my_item_type), enabling it inside Content Browser is done with the following minimum configuration, which defines the item human readable name, the template used to render the item preview and a list of columns:

netgen_content_browser:
    item_types:
        my_item_type:
            name: item_types.my_item_type # Will be translated with "ngcb" catalog
            preview:
                template: '@App/ngcb/my_item_type.html.twig'
            columns:
                # At least a "name" column must exist
                name:
                    name: columns.name # Will be translated with "ngcb" catalog
                    value_provider: name # Using a built in "name" value provider
            default_columns:
                - name

For the list of all available configuration options, take a look at the configuration reference.

Creating a Symfony service for the backend¶

Every item type needs to have a Symfony service called backend. Backend’s job is to hook into the CMS and return the data from the CMS needed to build locations and items. Backend must only return the items of a single type, the one it is registered for.

Every backend needs to implement Netgen\ContentBrowser\Backend\BackendInterface, which defines the number of methods used by the user interface to fetch the locations and items. Most of these methods are straightforward. They either return a list of locations/items under specified location or with the specified name, or a single location/item with provided ID.

getDefaultSections method should return a list of LocationInterface objects that will act as root locations of different sections of the location tree. For example, eZ specific backend would return three LocationInterface objects here, the one representing “Home” eZ location, the one representing “Media” eZ location and the one representing “Users” eZ location.

Once implemented, backend needs to be registered in Symfony DIC and connected to the item type by using netgen_content_browser.backend tag:

app.content_browser.backend.my_item_type:
    class: AppBundle\ContentBrowser\Backend\MyItemTypeBackend
    tags:
        -  { name: netgen_content_browser.backend, item_type: my_item_type }

Creating `ItemInterface` and `LocationInterface` objects¶

As already mentioned, backend needs to return objects implementing Netgen\ContentBrowser\Item\LocationInterface and Netgen\ContentBrowser\Item\ItemInterface, that represent Content Browser locations and items, respectively. It is up to you to implement these objects, either by building them directly in the backend, using a dedicated service to build them or in some other way you find appropriate. ItemInterface object will be injected in all templates (either when rendering a preview of an item or a single column), so make sure that it contains any data that you will need to render the templates.

Creating a preview template for the item¶

As already mentioned, you can enable a preview of your items with the following configuration:

netgen_content_browser:
    my_item_type:
        preview:
            template: '@App/ngcb/my_item_type.html.twig'

Creating this template is a simple task. The template receives the item in question in an item variable, which you can use to render the template.

Implementing columns rendered via templates¶

Content Browser allows you to implement your custom columns by specifying a template that will be used to render the cell data in the column.

To enable this behaviour, simply specify that a template should be used in your column definition:

netgen_content_browser:
        my_item_type:
        columns:
            column_one:
                name: columns.my_item_type.column_one
                template: '@App/ngcb/my_item_type/column_one.html.twig'

Just as with a preview template, creating this template is a simple task. Again, the template receives the item in question in an item variable, which you can use to render the template.

Implementing columns rendered via column value providers¶

If rendering a column via Twig template is not suitable for you, you can use a separate Symfony service to render the cell data of a column.

To create the service, you need to implement Netgen\ContentBrowser\Item\ColumnProvider\ColumnValueProviderInterface interface. This interface has a single getValue method which receives the item in question and should return a value that will be displayed inside the cell.

Once you create the service, register it in Symfony DIC, tag it with netgen_content_browser.column_value_provider tag and attach a unique identifier to the tag:

app.content_browser.template_value_provider.my_item_type.column_two:
    class: AppBundle\ContentBrowser\ColumnValueProvider\MyItemType\ColumnTwo
    tags:
        - { name: netgen_content_browser.column_value_provider, identifier: my_item_type\column_two }

After that, you simply need to reference the identifier of the value provider in column definition:

netgen_content_browser:
    my_item_type:
        columns:
            column_two:
                name: columns.my_item_type.column_two
                value_provider: my_item_type\column_two

Implementing a custom column for existing item types¶

Implementing a custom column for existing item types is not any different from implementing a column for your own custom item type.

The process involves adding a bit of configuration to enable the column:

netgen_content_browser:
    ezlocation:
        columns:
            my_column:
                name: columns.ezlocation.my_column
                # Either specify a template or a value provider identifier
                template: '@App/ngcb/ezlocation/my_column.html.twig'
                # value_provider: ezlocation\my_column

And then you need to either create a template that will render the cell of the column, or create and register a Symfony service that does the same. For more details, read the relevant sections in the chapter about creating a custom backend.

Usage in Symfony forms¶

Netgen Content Browser supports calling the browser from Symfony forms. To facilitate this, three custom Symfony form types have been implemented:

Single content browser type
Multiple content browser type
Dynamic content browser type

Requirements¶

Before you can use the Content Browser, you need to include its assets in your page head:

<meta name="ngcb-base-path" content="{{ path('ngcb_root') }}">
<link rel="stylesheet" href="{{ asset('netgen-content-browser.css', 'ngcb_css') }}">
<script src="{{ asset('netgen-content-browser.js', 'ngcb_js') }}"></script>

or just include the provided Twig template:

{% include '@NetgenContentBrowser/page_head.html.twig' %}

All HTML code blocks which have js-input-browse CSS class will be automatically initialized on document ready with jQuery and the plugin which are included in netgen-content-browser.js.

If you use another CSS class, or if you add content browser HTML code via AJAX to your page, you will need to manually initialize the plugin on those elements:

// ngc_jquery variable holds jQuery included with Netgen Content Browser
ngc_jquery('.js-input-browse').input_browse();

Single content browser type¶

Single content browser type allows you to select a single item of a predefined item type.

Form type class¶

Netgen\ContentBrowser\Form\Type\ContentBrowserType

Available options¶

item_type

This option defines which item type will the browser select

type: string, required: Yes
start_location

This option defines in which location the Content Browser will start.

type: int, required: No, default value: null

Other options¶

Parent of this type is the Symfony TextType type, so any options available in that type can be used in this type too.

Multiple content browser type¶

Multiple content browser type allows you to select one or more items of a predefined item type.

Form type class¶

Netgen\ContentBrowser\Form\Type\ContentBrowserMultipleType

Available options¶

item_type

This option defines which item type will the browser select

type: string, required: Yes
min

This option defines how many items must at least be selected before the dialog can be closed. Use null to disable the limit.

type: int, required: No, default value: null
max

This option defines how many items must at maximum be selected for dialog to be closed. Use null to disable the limit.

type: int, required: No, default value: null
start_location

This option defines in which location the Content Browser will start.

type: int, required: No, default value: null

Other options¶

Parent of this type is the Symfony CollectionType type, so any options available in that type can be used in this type too.

Dynamic content browser type¶

Dynamic content browser type allows you to select a single item, however, in contrast to ContentBrowserType type, this type allows you to select the item type before calling the dialog.

This type is the composite one, meaning it is constructed from two child forms, one that will hold the selected item type (named item_type) and the one that will hold the selected item ID (named item_id).

Form type class¶

Netgen\ContentBrowser\Form\Type\ContentBrowserDynamicType

Available options¶

item_types

This option defines which item types will be available to select from

type: array of string values, required: Yes
start_location

This option defines in which location the Content Browser will start.

type: int, required: No, default value: null

Usage in HTML¶

Content browser can be called at will anywhere from your HTML code by including a piece of specially crafted HTML.

Requirements¶

Before you can use the Content Browser, you need to include its assets in your page head:

<meta name="ngcb-base-path" content="{{ path('ngcb_root') }}">
<link rel="stylesheet" href="{{ asset('netgen-content-browser.css', 'ngcb_css') }}">
<script src="{{ asset('netgen-content-browser.js', 'ngcb_js') }}"></script>

or just include the provided Twig template:

{% include '@NetgenContentBrowser/page_head.html.twig' %}

All HTML code blocks which have js-input-browse CSS class will be automatically initialized on document ready with jQuery and the plugin which are included in netgen-content-browser.js.

If you use another CSS class, or if you add content browser HTML code via AJAX to your page, you will need to manually initialize the plugin on those elements:

// ngc_jquery variable holds jQuery included with Netgen Content Browser
ngc_jquery('.js-input-browse').input_browse();

Calling the Content Browser from your HTML¶

Use the following piece of HTML code to call the Content Browser, and replace the relevant pieces of data to suit your needs (item type, CSS ID for the value input and data- attributes).

After you select some items and close the Content Browser dialog, selected value will be available in a hidden input with a js-value CSS class.

Take care not to remove or change any other predefined CSS classes or HTML structure as this will break the Content Browser dialog.

data- attributes are all optional. data- attributes modify the behaviour of the interface, like limiting the number of items which can be selected, or showing/hiding certain aspects of the interface. One special data- attribute is used to modify the behaviour of the backend, by transferring it to the backend via query parameters. Basically, every data- attribute which starts with data-custom-, will be transferred to the backend so you can use it to modify the behaviour as you see fit. In the backend, you can inject the configuration object, as explained in the list of available Symfony services, which will then hold the list of all custom parameters.

Tip

To help you reach the selected value, you can attach custom CSS ID to hidden input where value is stored, as shown below.

<div class="js-input-browse item-empty"
    data-min_selected="1"
    data-max_selected="1"
    data-start_location="42"
>
    <div class="input-browse">
        <span class="js-clear"><i class="material-icons">close</i></span>

        <a class="js-trigger" href="#">
            <span class="js-name" data-empty-note="No item selected">Select an item</span>
        </a>
    </div>

    <input type="hidden" class="js-config-name" value="MY_ITEM_TYPE" />
    <input type="hidden" class="js-value" id="CSS_ID" value="" />
</div>

Calling the Content Browser from your Twig template¶

Alternatively, you can just use a handy Twig template and set the wanted options via an include tag:

{% include '@NetgenContentBrowser/content_browser.html.twig'
    with {
        input_id: 'my-location',
        item_type: 'ezlocation',
        item_name: 'My item',
        no_item_message: 'No item selected',
        required: false,
        min: 2,
        max: 3,
        custom_params: {param1: 'value1', param2: ['value2', 'value3']},
        start_location: 42,
        show_tree: true,
        show_search: false,
        show_preview: true
    }
%}

The following lists all available parameters that can be transferred to the template.

Required parameters¶

input_id

ID of the input where selected value will be placed, required

type: string
item_type

Item type to select in the dialog, required

type: string

Optional parameters¶

item_name

Item name to render when you already have a value

type: string
no_item_message

Message to show if no value is selected

type: string
required

If undefined or set to false, will render a button to clear the value

type: bool
min

Minimum number of items to select, defaults to configuration if undefined

type: int
max

Maximum number of items to select, defaults to configuration if undefined

type: int
custom_params

The list of custom parameters to transfer to the backend

type: array
start_location

This option defines in which location the Content Browser will start

type: int
show_tree

Whether to show the tree or not, defaults to configuration if undefined

type: bool
show_search

Whether to show the search or not, defaults to configuration if undefined

type: bool
show_preview

Whether to show the preview or not, defaults to configuration if undefined

type: bool

Usage in JavaScript¶

Content Browser can be called at will anywhere from your JavaScript code.

Requirements¶

Before you can use the Content Browser, you need to include its assets in your page head:

<meta name="ngcb-base-path" content="{{ path('ngcb_root') }}">
<link rel="stylesheet" href="{{ asset('netgen-content-browser.css', 'ngcb_css') }}">
<script src="{{ asset('netgen-content-browser.js', 'ngcb_js') }}"></script>

or just include the provided Twig template:

{% include '@NetgenContentBrowser/page_head.html.twig' %}

All HTML code blocks which have js-input-browse CSS class will be automatically initialized on document ready with jQuery and the plugin which are included in netgen-content-browser.js.

If you use another CSS class, or if you add content browser HTML code via AJAX to your page, you will need to manually initialize the plugin on those elements:

// ngc_jquery variable holds jQuery included with Netgen Content Browser
ngc_jquery('.js-input-browse').input_browse();

Calling the Content Browser from your JavaScript¶

TBD

eZ Platform integration¶

This section provides a handful of recipes with which you can learn how to extend eZ Platform integration in content browser.

eZ Platform integration¶

This section provides a handful of recipes with which you can learn how to extend eZ Platform integration in content browser.

Custom preview template for eZ content types¶

Implementing custom preview templates for eZ Platform content types is as easy as adding a new eZ view type in your content view configuration.

For every content type you wish to add the preview for, you need to define an override template for ngcb_preview view type, which will then automatically be used by the Content Browser to display the preview.

For example, to add the preview for your custom content type with identifier my_content_type, add the following config to your eZ Platform config:

ezpublish:
    system:
        default:
            content_view:
                ngcb_preview:
                    my_content_type:
                        template: '@App/ngcb/preview/my_content_type.html.twig'
                        match:
                            Identifier\ContentType: my_content_type

@App/ngcb/preview/my_content_type.html.twig is then a regular eZ Platform content view template, meaning you have access to content and location variables, which you can use to render what ever you wish.

Custom backend parameters¶

eZ location and eZ content backends support two custom parameters for now:

Overriding content types which will be shown in the tree
Overriding content types which will be selectable

Overriding content types which will be shown in the tree¶

To override which content types will be used to build the location tree, use location_content_types custom parameter, e.g.:

<div class="js-input-browse item-empty"
    data-custom-location_content_types="folder,category"
>
    ...
</div>

or in case of Twig template usage:

{% include '@NetgenContentBrowser/content_browser.html.twig'
    with {
        input_id: 'my-location',
        item_type: 'ezlocation',
        custom_params: {location_content_types: ['folder', 'category']}
    }
%}

Overriding content types which will be selectable¶

To override which content types will be selectable in the list of items, use allowed_content_types custom parameter, e.g.:

<div class="js-input-browse item-empty"
    data-custom-allowed_content_types="news,blog_post"
>
    ...
</div>

or in case of Twig template usage:

{% include '@NetgenContentBrowser/content_browser.html.twig'
    with {
        input_id: 'my-location',
        item_type: 'ezlocation',
        custom_params: {allowed_content_types: ['news', 'blog_post']}
    }
%}

Netgen Content Browser Documentation¶

Reference¶

Reference¶

Installation instructions¶

Use Composer¶

Activate the bundle¶

Activate the routes¶

Install assets¶

Configuration reference¶

Item type configuration¶

name¶

min_selected¶

max_selected¶

parameters¶

tree¶

search¶

preview¶

columns¶

default_columns¶

Full configuration example¶

Available Symfony services¶

netgen_content_browser.registry.backend¶

Configuration services¶

Symfony dependency injection tags¶

netgen_content_browser.backend¶

netgen_content_browser.column_value_provider¶

Upgrades¶

Upgrades¶

Upgrading from 0.7.0 to 0.8.0¶

Upgrade composer.json¶

Breaking changes¶

Upgrading from 0.8.0 to 0.9.0¶

Upgrade composer.json¶

Breaking changes¶

The cookbook¶

The cookbook¶

Implementing a custom backend¶

Configuring and enabling your new item type¶

Creating a Symfony service for the backend¶

Creating ItemInterface and LocationInterface objects¶

Creating a preview template for the item¶

Implementing columns rendered via templates¶

Implementing columns rendered via column value providers¶

Implementing a custom column for existing item types¶

Usage in Symfony forms¶

Requirements¶

Single content browser type¶

Form type class¶

Available options¶

Other options¶

Multiple content browser type¶

Form type class¶

Available options¶

Other options¶

Dynamic content browser type¶

Form type class¶

Available options¶

Usage in HTML¶

Requirements¶

Calling the Content Browser from your HTML¶

Calling the Content Browser from your Twig template¶

Required parameters¶

Optional parameters¶

Usage in JavaScript¶

Requirements¶

Calling the Content Browser from your JavaScript¶

eZ Platform integration¶

eZ Platform integration¶

Custom preview template for eZ content types¶

Custom backend parameters¶

Overriding content types which will be shown in the tree¶

Overriding content types which will be selectable¶

`name`¶

`min_selected`¶

`max_selected`¶

`parameters`¶

`tree`¶

`search`¶

`preview`¶

`columns`¶

`default_columns`¶

`netgen_content_browser.registry.backend`¶

`netgen_content_browser.backend`¶

`netgen_content_browser.column_value_provider`¶

Upgrade `composer.json`¶

Upgrade `composer.json`¶

Creating `ItemInterface` and `LocationInterface` objects¶