Skip to content

Define reusable configuration

Edit this page

The CKEditor bundle provides an advanced configuration which can be reused on multiple CKEditor instances. Instead of duplicate the configuration on each form builder, you can directly configure it once and reuse it all the time. The bundle allows you to define as many configurations as you want.

Tip

Check out the full list of CKEditor configuration options.

Define a configuration

1
2
3
4
5
6
7
8
9
# app/config/config.yml
fos_ck_editor:
    configs:
        my_config:
            toolbar: [ ["Source", "-", "Save"], "/", ["Anchor"], "/", ["Maximize"] ]
            uiColor:                "#000000"
            filebrowserUploadRoute: "my_route"
            extraPlugins:           "wordcount"
            # ...

Tip

The config node is a variable node meaning you can put any CKEditor configuration options in it.

Note

The first configuration defined will be used as default configuration if you don't explicitly configure it.

Use a configuration

When you have defined a config, you can use it with the config_name option:

1
2
3
$builder->add('field', 'ckeditor', array(
    'config_name' => 'my_config',
));

Override a configuration

If you want to override some parts of the defined config, you can still use the config option:

1
2
3
4
$builder->add('field', 'ckeditor', array(
    'config_name' => 'my_config',
    'config'      => array('uiColor' => '#ffffff'),
));

Define default configuration

If you want to define your configuration globally to use it by default without having to use the config_name option, you can use the default_config node:

1
2
3
4
5
6
# app/config/config.yml
fos_ck_editor:
    default_config: my_config
    configs:
        my_config:
            # ...
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.
TOC
    Version