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.I have a them under development that uses bartik as a base theme. I just re-organized my css files and added layout.css and reset.css files. As the attached file shows, my files are now being loaded in the same sequence as if I was loading the bartik files. It means that my layout file is now loaded before bartiks style.css. Since bartik's style.css has layout statements, they are now overriding the statements in my layout.css, breaking the layout.
Is this the way it is supposed to work? Does this happen if I name a css file the same as a core css file? How is the order determined?
I know I can rename my files, but layout and reset are common names in many themes. I tried searching documentation without much success. If this just my ignorance, then it can be closed quickly.
| Comment | File | Size | Author |
|---|---|---|---|
| sourceout.pdf | 20.55 KB | dcrocks |
Comments
Comment #1
dcrocks CreditAttribution: dcrocks commentedComment #2
Jeff Burnz CreditAttribution: Jeff Burnz commentedYes, I would consider this as "by design", the layout.css only loads what I would call macro layout - page and region type layout (I think there is one reference to blocks for the #featured region, which probably should be in style.css).
The way to override style.css is to add another stylesheet, such as "mytheme.css" and do your style.css overrides in that.
Comment #3
dcrocks CreditAttribution: dcrocks commentedUnderstand, but but not in complete agreement. Seems the way to fully use a theme as a base is to have a mylayout, mystyle, mycolors, myreset, etc., which of course doubles the number of files loaded. Or simply copy and modify the original themes files and not bother with base theme specification. Seems like the new theme files should always be loaded after all base theme files while removing duplicate base theme file names from the load list. Placing new theme files in the same load position as duplicate named base theme files seems counter-intuitive.
Comment #4
Kars-T CreditAttribution: Kars-T commentedDear fellow Drupal enthusiasts,
this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not pose the problem comprehensible.
But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.
Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.
Help can also be found for it on IRC and in the user groups.
In order this issue no longer remains, I put this issue to "fixed".
If there is new information, please re-open the issue.
Comment #5
dcrocks CreditAttribution: dcrocks commentedI'm sorry, but if this is just a documentation problem, then it still needs to be fixed. I still can't find documentation that says exactly how drupal handles css files with the same name as the base theme being over ridden. The closest I can find is http://drupal.org/node/263967. I am going to leave a comment there and see what develops.