Create the File App-Block

This chapter explains how to create a block to handle a file, which can be rendered on a page as a link and the UI to manage it.

In this chapter you will learn:

  1. How to add an App-Block to an existing bundle
  2. How to add a controller and a route to handle the implemented actions
  3. How to add an App-Block’s extra asset to RedKite CMS
  4. How to execute a javascript when the editor popover is opened


This chapter requires as pre-requisite the reading of the Add a new App-Block chapter

Add an App-Block to an existing bundle

An App-Block can live as a standalone bundle or it can be packed together with other App-Blocks in a single bundle. Thhis means that a bundle can handle one or more App-Blocks.

The block, we are going to create, does not tie so much with the block created in the Add a new App-Block but, just to explain how to add a block to an existing bundle, we will add this new App-Block to the BootstrapButtonTutorialBlockBundle.

The App-Block class

To add the new App-Block class to the BootstrapButtonTutorialBlockBundle, just create the BlockManagerFileTutorial.php file inside the BootstrapButtonTutorialBlockBundle/Core/Block, open it and add the following code:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Core/Block/BlockManagerFileTutorial.php
namespace RedKiteCms\Block\BootstrapButtonTutorialBlockBundle\Core\Block;

use RedKiteLabs\RedKiteCms\RedKiteCmsBundle\Core\Content\Block\JsonBlock\BlockManagerJsonBlockContainer;;

class BlockManagerFileTutorial extends BlockManagerJsonBlockContainer
    public function getDefaultValue()
        $value =
            "0" : {
                "file" : "Click to load a file",
                "description" : ""

        return array(
            'Content' => $value,

This block’s default value is made by a json markup and it is defined by the file and description attributes, declared in the getDefaultValue method.

We must override the default renderHtml method to render the file as link, as follows:

use RedKiteLabs\RedKiteCms\RedKiteCmsBundle\Core\AssetsPath\AssetsPath;

protected function renderHtml()
    $items = $this->decodeJsonContent($this->alBlock);
    $item = $items[0];
    $file = $item['file'];

    $options = array(
        'webfolder' => $this->container->getParameter('red_kite_cms.web_folder'),
        'folder' => AssetsPath::getUploadFolder($this->container),
        'filename' => $file,

    $options['displayValue'] = (array_key_exists('description', $item) && ! empty($item['description'])) ? $item['description'] : $file;

    return array('RenderView' => array(
        'view' => 'BootstrapButtonTutorialBlockBundle:Content:File/file.html.twig',
        'options' => $options,

The AssetsPath provides the paths for common assets folders, in our block we need the upload folder, so we will use the getUploadFolder method, which is deputated to return this information.

This method renders the BootstrapButtonTutorialBlockBundle:File:file.html.twig which has not been created yet, so add the file.html.twig under the BootstrapButtonTutorialBlockBundle Resources/views/File folder, open it and add the following code:

{% extends "RedKiteCmsBundle:Block:Editor/_editor.html.twig" %}

{% block body %}
<a href="/{{ folder }}/{{ filename }}" {{ editor|raw }}>{{ displayValue }}</a>
{% endblock %}

Now RedKite CMS can render the block on the page. We just need to define the editor, so we need to override the editorParameters method to define the parameter to pass to the editor. Add the following code to the **BlockManagerFileTutorial*:

public function editorParameters()
    $items = $this->decodeJsonContent($this->alBlock);
    $item = $items[0];

    $formClass = $this->container->get('file_tutorial.form');
    $form = $this->container->get('form.factory')->create($formClass, $item);

    return array(
        'template' => 'RedKiteCmsBundle:Block:Editor/_editor_form.html.twig',
        'title' => Files editor,
        'form' => $form->createView(),

We don’t need to define a new editor template because we will use the _editor_form.html.twig provided by RedKiteCms.

The editor requires a form to manage its parameters. This form must be declared as a service called file_tutorial.form in the DIC.

Add the FileTutorialType.php under the BootstrapButtonTutorialBlockBundle/Core/Block/Form folder, open it and paste the following code inside:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Core/Form/FileTutorialType.php
namespace RedKiteCms\Block\BootstrapButtonTutorialBlockBundle\Core\Form;

use Symfony\Component\Form\FormBuilderInterface;
use RedKiteLabs\RedKiteCms\RedKiteCmsBaseBlocksBundle\Core\Form\Base\BaseType;

class FileTutorialType extends BaseType
    public function buildForm(FormBuilderInterface $builder, array $options)
        $builder->add('description', 'textarea');

        parent::buildForm($builder, $options);

We will override the RedKiteCmsBlockRedKiteCmsBaseBlocksBundleCoreFormBaseBaseType which provides some standard configurations like the form name. Feel free to give it a look to understnd hor it is designed.

Declare the App-Block and the form as services

To have to App-Bock working, we must open the app_block.xml and add the App-Block class as a service:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Resources/config/app_block.xml
    <parameter key="bootstrap_file_tutorial_block.block.class">RedKiteCms\Block\BootstrapButtonTutorialBlockBundle\Core\Block\BlockManagerFileTutorial</parameter>
    <parameter key="file_tutorial.form.class">RedKiteCms\Block\BootstrapButtonTutorialBlockBundle\Core\Form\FileTutorialType</parameter>

    <service id="bootstrap_file_tutorial_block.block" class="%bootstrap_file_tutorial_block.block.class%">
        <tag name="red_kite_cms.blocks_factory.block" description="File Tutorial" type="FileTutorialBlock" group="bootstrap,Twitter Bootstrap" />
        <argument type="service" id="service_container" />

    <service id="file_tutorial.form" class="%file_tutorial.form.class%">

Load a file

To load or update the file, we must use the Media Library that comes with RedKite CMS.

To accomplish this task we must add a javascript action, which takes care to open the media library and add the reference to the chosen file to the file input box.

The media library requires a connection to an action to initialize a connector to bind the media library itself with the server.

To accomplish this task, we must implement a controller with a dedicated route.

The controller

To add the controller simply create the new ElFinderFileTutorialController.php class file under the Controller folder, open it and add the following code:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Controller
namespace RedKiteCms\Block\BootstrapButtonTutorialBlockBundle\Controller;

use Symfony\Bundle\FrameworkBundle\Controller\Controller;

class ElFinderFileTutorialController extends Controller
    public function connectFileAction()
        $connector = $this->container->get('el_finder.file_tutorial_connector');

This action is really simple, in fact it gets the el_finder.file_tutorial_connector service and calls the connect method.

We don’t need to return a Response here because the connect method takes care to return the right data for us.

The ElFinderFileConnector service

The ElFinder service has not been created yet, so add a new ElFinderFileTutorialConnector.php class under the Core/ElFinder/File folder, open it and add the following code:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Core/ElFinder/File
namespace RedKiteCms\Block\BootstrapButtonTutorialBlockBundle\Core\ElFinder\File;

use RedKiteLabs\RedKiteCmsBundle\Core\ElFinder\Base\ElFinderBaseConnector;

class ElFinderFileTutorialConnector extends ElFinderBaseConnector
    protected function configure()
        return $this->generateOptions('files', 'Files');

This object inherits from a base connector object, you should give a look, and defines the mandatory configure method which returns an array of options, generated by the generateOptions method.

This last method requires a folder name as first argument and an alias displayed on the media library as second one.


For simplicity the folder name has been hardcoded, in the real world it should be declared as a container’s parameter.

This service must be declared in the Dependency Injector Container as follows:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Resources/config/app_block.xml
    <parameter key="el_finder.file_tutorial_connector">RedKiteCms\Block\BootstrapButtonTutorialBlockBundle\Core\ElFinder\File\ElFinderFileTutorialConnector</parameter>

    <service id="el_finder.file_tutorial_connector" class="%el_finder.file_tutorial_connector%" >
        <argument type="service" id="service_container" />

The route for the controller

To run that action we must create a new route, so create the file.xml file under the Resources/config/routing/file, open it and add the following code inside:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Resources/config/routing/file
<?xml version="1.0" encoding="UTF-8" ?>

<routes xmlns=""

    <route id="_file_connect" pattern="/backend/{_locale}/al_elFinderFileTutorialConnect">
        <default key="_controller">BootstrapButtonTutorialBlockBundle:ElFinderFileTutorial:connectFile</default>
        <default key="_locale">en</default>

Now we must create a routing.yml file under the Resources/config folder, open it and add the following code:

    resource: "@BootstrapButtonTutorialBlockBundle/Resources/config/routing/file/file.xml"

When you add a routing.yml file under a bundle managed by the RedKiteLabsBootstrapBundle, this last one takes care to autoload the routes for you.

The javascript asset

Everything is ready, so we just need to add a javascript asset, to open the media library.

Create a new file_tutorial_editor.js under the Resources/public/file/js folder, open it and add the following code:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Resources/public/file/js/file_tutorial_editor.js
$(document).ready(function() {
    $(document).on("popoverShow", function(event, element){
        if (element.attr('data-type') != 'FileTutorialBlock') {

        // your code

This code responds to the popoverShow event triggered when the editor popover is opened.

This event passes as second argument, the element which is being edited, so we must check that it belongs the block type we are working on, in this example the FileTutorialBlock.

Now we will add the code to open the media library under the [ your code ] section:

        url : frontController + 'backend/' + $('#al_available_languages option:selected').val() + '/al_elFinderFileTutorialConnect',
        lang : 'en',
        width : 840,
        destroyOnClose : true,
        commandsOptions : {
            getfile: {
                oncomplete: 'destroy'
        getFileCallback : function(file, fm) {

First of all, we bind the al_json_block_file event click, so each time the users click inside the file inputbox, the media library is opened.

The most important options to point out here are the url, which executes the action we implemented before and the getFileCallback which sets back the file path.

Add the asset to the cms

The last thing to do is to add this asset to the cms. This task is made adding a parameter to the DIC, so open the app_block.xml file and add the following code inside:

// src/RedKiteCms/Block/BootstrapButtonTutorialBlockBundle/Resources/config/app_block.xml
    <parameter key="file.external_javascripts.cms" type="collection">

This parameter is parsed by RedKite CMS and added to the external javascripts only when the editor is active to avoid loading this asset in production.

This last task is made adding the cms suffix to the file.external_javascripts key.

Use your App-Block

To use your new App-Block, enter inside RedKite CMS backend and just add it to your website from the adder blocks menu.


After reading this chapter you should be able to add an App-Block to an existing bundle, add a controller and a route to handle the implemented actions, add an App-Block’s extra asset to RedKite CMS, override the default action to save the block’s content

Found a typo ? Something is wrong in this documentation ? Just fork and edit it !

Fork me on GitHub