By ikati on

I've been reading the documentation about making changes to the theme. I don't want to make major changes.. just some minor ones.

but, I can't figure out where to put my additional CSS stylesheet. do I put it in /themes/garland? or do I put it in /site/all/themes/garland (where my additional CSS stylesheet would be the only member)?

I would put this in .info, right?:

Add a stylesheet for all media
stylesheets[all][] = style.css
stylesheets[all][] = mystyle.css

so that the default "style.css" would still be used, but my stylesheet would also be called?

thanks for any help.

⋅ Categories: Drupal 6.x

Comments

ikati’s picture

ikati commented

Just bumping this because I think the answer has to be simple. (and probably right in front of my eyes.. but I can't find it)

Lynne

Wolfflow’s picture

Wolfflow commented

Maybe duplicate,

I started a post here http://drupal.org/node/236591
maybe it helps you out!

Cheers

Share your experience with the Open Source Community
it's not only a choice but a Life Philosophy !!!
http://www.adaccs.at : A Drupal advanced CSS Content System - Community Project

Contact me for drupal projects in English, German, Italian, Drupal Hosting Support.

ikati’s picture

ikati commented

I'm still confused. I guess I don't know what "if you specify it in the .info, then it will get your local copy". but.. where do you upload your local copy to?

I want to add to the garland.info file this statement:
[code]
; Add a stylesheet for all media
stylesheets[all][] = MYStyle.css[/code]

where will drupal think MYStyle.css is?

do I upload MYStyle.css to:

http://www.mysite.com/themes/garland/

or

http://www.mysite.com/sites/all/themes/garland/

the documentation seems to imply that you put any changes to the themes in the sites/all/themes/garland/ folder ... not the /themes/garland/ folder.

so.. is the "local" copy assumed to be in /sites/all/themes?

Wolfflow’s picture

Wolfflow commented

...

Well as I have understand but not implemented yet with Drupal 6 the CSS system was somehow
expanded. ( A great achieveness, in my opinion!!) You can now influence with CSS theming each
Core Module without having to Hack the Core Module it's self.

So the approach described above is one that goes more deeply in costomize the Theme Output.
The method below described by Proudleo is correct and much simple.

So do not esitate to send us your feedback!!!

Cheers

Contact me for drupal projects in English, German, Italian, Drupal Hosting Support.

proudleo’s picture

proudleo commented

...I would do this..

Copy your Garland theme to sites/all/themes and put your style there. Rename that theme to something else so it shows up with a different name in Admin/Site building/Themes. That way, if it doesn't work you can just delete it and hopefully someone with more experience could help you better here...lol. Seems to be a safe way to do it without crashing the site or losing anything.

Of course, this could be the absolute worst way to do it, but I'm just going off the basics in the Pro Drupal Development book.

P.S. Lemme know if you choose to do that and if it works, please....

ikati’s picture

ikati commented

my changes are simple.. but I wanted to keep my changes separate from the "vanilla" drupal garland theme. This is because if there are any updates to the Garland theme (or whatever theme I'm using as the base theme).. then I just want to be able to upload the new version without having to figure out what I changed. putting my changes to css in a separate folder, the /site/all/themes folder would do this, and I thought from reading the documentation, that this was the purpose of this folder.

but.. I'm still playing around with it. I had to drop it for a while to fix something else (unrelated).

anyway, I wish to keep my modifications separate.. it just makes it so much easier to keep the website up to date with whatever new versions of core modules and themes become available.

thanks so much for the input, everyone. I appreciate it being a drupal newbie. I've read the documentation, and have a drupal book.. but sometimes it is still confusing as to where to individualize your website, once you have drupal up and running. Hearing how different users approach these problems really helps.

Lynne