[support] overriding a theme's css

[Brian Choc]

Any CSS you put in the theme folder should come in after the CSS is in the
modules.  You don't need to append your css to an existing style sheet.  You
can add a new style sheet and add its name to the .info file, if that's
easier.

On Wed, Dec 22, 2010 at 9:21 PM, Marty Landman
<mlandman at face2interface.com>wrote:

> Yeah I was afraid of that. Wish there was something like overriding
> the tpl.php files but nooo. And alas I didn't write the site to begin
> with so too late for doing things right to start with.
>
> Marty
>
> At 08:44 PM 12/22/2010, Brian Choc wrote:
> >You could use 'diff' or something similar to find out what's changed
> >and put just those lines of CSS in a file in your theme
> >folder.  Generally, I find the best way to avoid this problem is not
> >to get into it in the first place by keeping the custom CSS in the
> >theme folder to begin with.  :)
> >
> >Brian
> >
> >On Wed, Dec 22, 2010 at 5:52 PM, Marty Landman
> ><<mailto:mlandman at face2interface.com>mlandman at face2interface.com> wrote:
> >I've upgraded a D5 website for a client and the CSS files for
> >nice_menus had been customized within the nice_menus module's
> >directory, which obviously got overwritten by my upgrade.
> >
> >Which I understand is why this wasn't the right way to do things. I'm
> >sure that copying the old css files fixes the problems, because I
> >did. Want to do things according to best practice. I could just take
> >those entire css file contents and append them to the style.css file
> >for the theme. That'd work I think, but is there a better way, w/o
> >actually picking all the lines apart to see what's needed?
> >
> >Marty
> >
> >--
> >[ Drupal support list | <http://lists.drupal.org/>
> http://lists.drupal.org/ ]
> >
> >
> >
> >
> >--
> >[ Drupal support list | http://lists.drupal.org/ ]
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20101223/d74dd11d/attachment.html