What I did was create a “custom.css” file in custom/themes/Suite7/css
with just my changes thinking that it would copy this in. But it doesn’t.
I will try what you have suggested and report back here.
Might I suggest that you put a link the html ‘header’ file (wherever that is) to a custom.css file (somewhere) and provide that file for people to put in overrides, etc, and make that file update proof.
I did exactly what you said to do… worked great… now I won’t have to do it each time I do an upgrade.
What is interesting is that Suite has theme css in lots of different places. It looks like doing a Quick Repair to put the style.css file in cache/[theme]/css, which makes no sense to me… unless it pulls from there to put it into the database (which would also make no sense.) Why the cache directory?
It would be very simple for the developers to create a file called custom.css and put a link in the .tpl file (or wherever Suite has it’s header HTML) to pull in an overrides…
<link rel="stylesheet" type="text/css" href="cache/themes/Suite7/css/style.css
<link rel="stylesheet" type="text/css" href="cache/themes/Suite7/css/custom.css
<p>and why does it call in this:</p>
<link rel="stylesheet" type="text/css" href="cache/themes/Suite7/css/deprecated.css?v=TD_H7l-9zrxdpy4SI4D5Xg"
Why would you want to bring in a deprecated version?