You are browsing the documentation for version 4.1 of OroCommerce, OroCRM and OroPlatform, which is no longer maintained. Security Support ends in January 2023. Read version 5.0 (the latest LTS version) of the Oro documentation to get the updated information.
See our Release Process documentation for more information on the currently supported and upcoming releases.
assets.yml file can be used to define CSS file groups. The listed files will be
automatically merged and optimized for web presentation.
The following example creates two groups (
second_group) each of them
containing three CSS files:
1 2 3 4 5 6 7 8 9 10 11
# src/Acme/DemoBundle/Resources/config/oro/assets.yml assets: css: first_group: - 'First/Assets/Path/To/Css/first.css' - 'First/Assets/Path/To/Css/second.css' - 'First/Assets/Path/To/Css/third.css' second_group: - 'Second/Assets/Path/To/Css/first.css' - 'Second/Assets/Path/To/Css/second.css' - 'Second/Assets/Path/To/Css/third.css'
By default, when you install the application’s assets using the
assets:install command, all
CSS files from all groups and all bundles will be merged and optimized.
For debugging purposes compression of CSS files of certain groups can be disabled with the
1 2 3
oro_assetic: css_debug: - first_group
You can use the
oro:assetic:groups command to get a list of all available groups.