Customizing the Application Layout¶

Creating and Embedding Custom Stylesheets¶

Using your own CSS files is pretty simple. Just save them in the, for example, Resources/public/css/ directory of your bundle and list them in the assets.yml configuration file:

1
2
3
4
5
6
7
8
9

# src/Acme/DemoBundle/Resources/config/oro/assets.yml
assets:
    css:
        frontend:
            - 'bundles/acmedemo/css/frontend/first.css'
            - 'bundles/acmedemo/css/frontend/second.css'
        backend:
            - 'bundles/acmedemo/css/backend/first.css'
            - 'bundles/acmedemo/css/backend/second.css'

Then, embed your styles in the main layout template using the oro_css Twig tag:

1
2
3

{% oro_css filter='filters,separated,by,comma' output='css/style.css' %}
    <link rel="stylesheet" media="all" href="{{ asset_url }}" />
{% endoro_css %}

Now, you need to clear the cache and install the new stylesheets by running the assets:install command:

$ php app/console cache:clear
$ php app/console oro:assets:install
$ php app/console assetic:dump

In this example, all four CSS files from your bundle as well as all the other files from the Oro Platform and from third party bundles will be merged and dumped in the web/css/style.css file. Optionally, you can apply different filters to each CSS file (separate them by comma if you want to apply multiple filters.

Debugging Your Stylesheets¶

As you can see in the example above, you can group your CSS files. This is extremely useful when you have to debug your stylesheets. By default, all CSS files will be merged and minimized in a single file. If you need to debug certain CSS files, you can exclude groups from the build process which means that all files belonging to an excluded group won’t be merged and compiled.

For instance, the following configuration excludes all files from the frontend group:

1
2
3

# app/config.yml
oro_assetic:
    css_debug: [frontend]

$ php app/console oro:assetic:groups

Application-specific Themes¶

Customizing the layout of your Platform application is as easy as defining your custom theme in your application’s configuration using the oro_theme option:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

# app/config.yml
oro_theme:
    themes:
        mytheme:
            styles:
                - mytheme/css/main.css
                - mytheme/css/ie.css
            label: My Theme
            icon: mytheme/images/favicon.ico
            logo: mytheme/images/logo.png
            screenshot: /mytheme/images/screenshot.png
    active_theme: mytheme

First, you create a theme named mytheme whose label is My Theme and that makes use of the two CSS files main.css and ie.css. Secondly, you just have select the theme to be used by setting its name as the value of the active_theme option.

Reusable Themes¶

Sometimes, you do not only want to customize your own application, but you like to provide a theme that can be reused in different applications. To achieve this, simply specify the theme’s options in a file named settings.yml that is located in the Resources/public/themes/<theme-name> directory of your bundle:

1
2
3
4
5
6
7
8

# src/Acme/DemoBundle/Resources/public/themes/acme-theme/settings.yml
styles:
    - bundles/acmebundle/themes/acme-theme/css/main.css
    - bundles/acmebundle/themes/acme-theme/css/ie.css
label: Acme Demo Theme
icon: bundles/acmebundle/themes/acme-theme/images/favicon.ico
logo: bundles/acmebundle/themes/acme-theme/images/logo.png
screenshot: bundles/acmebundle/themes/acme-theme/images/screenshot.png

To use the theme in any application, enable it in the application configuration:

1
2
3

# app/config.yml
oro_theme:
    active_theme: acme-theme

List of available themes:
acme-theme (active)
 - label: Acme Demo Theme
 - logo: bundles/acmebundle/themes/acme-theme/images/logo.png
 - icon: bundles/acmebundle/themes/acme-theme/images/favicon.ico
 - screenshot: bundles/acmebundle/themes/acme-theme/images/screenshot.png
 - styles:
     - bundles/acmebundle/themes/acme-theme/css/main.css
     - bundles/acmebundle/themes/acme-theme/css/ie.css
demo:
 - label: Demo Theme
 - logo: bundles/oroui/themes/demo/images/favicon.ico
 - styles:
     - bundles/oroui/themes/demo/css/less/main.less
     - bundles/oroui/themes/demo/css/style.css
mytheme
 - label: My Theme
 - logo: mytheme/images/logo.png
 - icon: mytheme/images/favicon.ico
 - screenshot: mytheme/images/screenshot.png
 - styles:
     - mytheme/css/main.css
     - mytheme/css/ie.css
oro
 - label: Oro Theme
 - icon: bundles/oroui/themes/oro/images/favicon.ico
 - styles: bundles/oroui/themes/oro/css/style.css

Finally, clear the cache and dump all assets:

$ php app/console cache:clear
$ php app/console assets:install
$ php app/console assetic:dump

Overriding a Theme¶

The configuration files of all available themes are merged when the service container is being compiled. Since the merge process does override values if they are defined in more than one file, you can make use of it when you are in the need to customize an existing theme.

For example, imagine that you want to use the Oro theme from the OroUIBundle, but you want to use a custom label and favicon for it. The definition of the Oro theme as defined in the bundle looks like this:

1
2
3
4

label: Oro Theme
icon: bundles/oroui/themes/oro/images/favicon.ico
styles:
    - bundles/oroui/themes/oro/css/style.css

All you have to is placing a settings.yml file in the Resources/public/themes/oro directory of your bundle and define the values you want to change:

1
2
3

# src/Acme/DemoBundle/Resources/public/oro/
label: Custom Oro Theme
icon: images/custom_favicon.ico

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

// app/AppKernel.php
// ...

class AppKernel extends OroKernel
{
    public function registerBundles()
    {
        $bundles = array(
            // ...
            new ThirdParty\Bundle\ThirdPartyBundle(),
            // ...
            new Acme\DemoBundle\AcmeDemoBundle(),
            // ...
        );

        // ...
    }

    // ...
}