The path logic is painful when using sub themes to overwriting libraries.
Lets say we have 2 themes : base and subtheme
If I want to remove the toolbar.theme.css in my basetheme (base) and i set my active theme set to "subtheme"
name: base
type: theme
base theme: classy
libraries-override:
toolbar/toolbar:
css:
theme:
css/toolbar.theme.css: false
subtheme:
name: subtheme
type: theme
base theme: base
core: '8.x'
Oki so that works fine toolbar.theme.css is removed when i use my subtheme, and it "inherits" the removing of toolbar.theme.css
But if I wanna do the same with a the theme that do not uses a subtheme i have to change the paths
name: basedrop
type: theme
base theme: stable # or classy
core: '8.x'
libraries-override:
toolbar/toolbar:
css:
theme:
/core/themes/stable/css/toolbar/toolbar.theme.css: false
The path for toolbar.theme.css have to be set to now to /core/themes/stable/css/toolbar/toolbar.theme.css instead of css/toolbar.theme.css: false thats kinda confusing
make paths for overwriting core allways be the same path
Closed: duplicate
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There are at least two comments, #5 and #11, that state that this problem is fixed in 🐛 Overriding already overridden libraries-override requires knowledge of previous libraries-overrides Needs work . And the has been no response to confirm if the suggestion in #14 fixes this, despite asking again 2 years ago.
Therefore I am closing this as a duplicate of that one.