How to turn the header's background color into white

I'd like to edit the header's background color to turn it into white. Wonder what file to edit for that.

Appreciate any guidance,thanks in advance

It is in the file general.css  in templates/base or templates/yourtemplatename under div.sys_main_logo

Thanks ggsink,

for some reason it didn't do it. Seems like some other script controls the logo area color. Even when I uploaded my logo to overide the default,my png logo's background turns black.

gginc provided the correct information.

If your dolphin cache is on, then clear it. Caching should also be turned off while working on the site.

If that does not help. The a URL to your site would be helpful. If your running a custom template there may be a color setting in a different div. In those cases we have to be able to find it. Thats the reason for a URL. This way we can use firebug to find the exact location and css file.

In

templates/base/css/general.css

Find on lines 154 - 159 the following code

div.sys_main_logo {
        position: relative;
        z-index: 56;

        background-color: #f4f4f4;
 }

Change to

 div.sys_main_logo {
        position: relative;
        z-index: 56;

        background-color: #FFFFFF;
 }

this should make the changes you are looking for, if it dont then try loging in to FTP and delete everything except the .htaccess from the cache folder.

Next delete everything in the cache_public folder

Now delete your web browsers cache also

reload your site

You should never make changes to /base/.  You can add an override to /tmpl_uni/css/general.css by adding the following at the end of the file (after the @import bit):

div.sys_main_logo {
    background-color: #fff;
}

Clear the cache after you're done.

nathan why cant you cange base?

 I have almost compleatly re done one dolphin site just in the base.

The other theme that comes with dolphin just links back to base anyway (not realy sure why they have one theme that just links back to the other in almost every file)

/base/ is more likely to be changed during upgrades, which means a lot (if not all) of your work done there will be undone.  /tmpl_uni/ is less likely to be changed because it calls everything from /base/.

I don't even touch /tmpl_uni/ when making changes.  I create a new template based on UNI and make all my changes there.  But again, the problem area is /base/.

Ok I never knew that however it has confused me now because uni has nothing in it just lines in every file linking back to base.

So I guess my question is how do you make a template from a template with nothing in but links to another template (im confused)

uni is missing all the guts base is the one with the guts in it.

If I wanted to make a new template to sell lets say, would I have to copy everything from bases files into uni's files for it to do what it is suposed to and not just link to some other thing

You're right, UNI only calls from /base/, but you can add to it.  For example, you can expand BxTemplMenu.php with code from BxBaseMenu.php.  You can also add CSS after the @import bit.

Alternatively, you can also copy UNI to create a new template, and then copy the contents of /base/ into it (except the contents of /scripts/, those are /base/-specific).  The point is not to edit /base/, because if changes are going to be made to the template, they will be made there.

cool thanks for pointing that out it is handy to know.

Now did this guy or gal get thier header sorted

 I quite got it heheh.
and let´s say that you have made all your work on Base and now you want to create a new template, like tmpl_mysite from Base.  But there are too much new files and changes that you can even remember where they are.  How to make it?  I mean, without using UNI.
  Should I copy the Base folder, rename to tmpl_mysite and replace the Script folder from UNI to my new template?

 Or
Is that not a good idea? 

You would need to use UNI as the base for the template.  You need to copy /tmpl_uni/ and use a name for the directory (e.g., /tmpl_foo/ or just /foo/), and then change the template name in /scripts/BxTemplName.php.  You can copy the contents of /base/ (except for /scripts/) into this new template, and then make all changes there.

If you're making a new template based on the changes you made in /base/, there shouldn't be a problem, as those will be carried over to the new template, as long as you really made all changes there.  You don't have to, but you should then replace /base/ with a vanilla copy, because my damaged mind says so.

You should never make changes to files without keep track of them.  I make changes in a repository and write all changes down in a file called changes.txt.  It can be a pain, but when it comes time to upgrade, it'll come in handy.

But this is all off-topic.  If you want to continue this, message me.

sorry, what is a Vanilla copy?

... got it!  After creating a new template, replace the BASE with a copy of the Original BASE (that is vanilla, right?)

 I have Dolphin D7.7 software downloaded.   In this case, all I have to do is to delete /BASE/ (that I have modified) and upload the original one.  Hope to be doing that correctly