Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It appears that the CSS ordering by default between Omega and sub-themes is a bit inconsistent. Need to make sure all Omega CSS is loaded first, followed by the sub-theme's implementations to ensure easier overrides of styles.
The first stylesheets it seems to load are from the stylesheets declared by the subtheme, including the layout CSS and the default empty CSS file in the starterkit(s)
@import url("/themes/omega/starterkits/omega_simple_starterkit/style/css/layout/primary-layout.css?ny17wz");
@import url("/themes/omega/starterkits/omega_simple_starterkit/style/css/omega_simple_starterkit.css?ny17wz");
After those, the libraries CSS included from the Omega settings is loaded.
@import url("/themes/omega/omega/style/css/base.css?ny17wz");
@import url("/themes/omega/omega/style/css/html-elements.css?ny17wz");
@import url("/themes/omega/omega/style/css/site-branding.css?ny17wz");
@import url("/themes/omega/omega/style/css/breadcrumbs.css?ny17wz");
@import url("/themes/omega/omega/style/css/main-menus.css?ny17wz");
@import url("/themes/omega/omega/style/css/messages.css?ny17wz");
@import url("/themes/omega/omega/style/css/pagers.css?ny17wz");
@import url("/themes/omega/omega/style/css/tabs.css?ny17wz");
This needs to be fixed for sure. Probably just an issue with either weighting, or the grouping of the loaded libraries.
Comments
Comment #2
himerus CreditAttribution: himerus as a volunteer commentedIt appears that changing all the optional Omega CSS to component type group works.
The new ordering should be as seen below. Note the layout.css is still above all the components and theme CSS, but that is okay as it is highly targeted and using the layout group for the layout file seems like the way to go.
Comment #3
himerus CreditAttribution: himerus as a volunteer commented