Important Upgrade from 1.6.0 to 1,6.4 - CSS issues

Hi folks, I have my own folder as template and it is set to use it in the kunena settings. By checking the files into the kunena 1.6.4 package upgrade, I didn't see any css file such as kunena.forum-min.css or kunena.forum.css to change the colors of my headers and topic texts. It was all changed back to blue and so on. I didn't get to find where it was changed once I'm using my own template set into Kunena settings as said before. The headers I got to put back the color by changing form Kunena/template manager by clicking on the template name and changing the "Forum header bg color", but there is no font color option. My doubt is, how can I change again my topic texts and links for the colors I want to if there was no update in any css file that I've noticed. Maybe I'm missing some other place.

I need to change the topic title colors and Kunena Ktop (thin line on the top). What file was upgraded that changed these colors?

Thanks in advance.

Hi thetoast, I'm sorry, but your reply didn't refresh a solution.

What is happening is that the upgrade is overwriting the CSS in my own template/folder which has the files kunena.forum-min.css and kunena.forum.css, so I wonder which file is controling now the topics titles colors/links colors and the ktop. as you can see here they are blue and I want brown back:
www.esferadobem.com.br/index.php?&lang=us

iLucato wrote: What is happening is that the upgrade is overwriting the CSS in my own template/folder ...

That is correct and that has always been the situation with Kunena. When you upgrade Kunena the installation overwrites all the files that were installed by the previous version. The only files that are not replaced are those that you added. If you change a file then the changes will be lost if the file you changed was in one of the standard file locations used by Kunena.

Obviously, this does not mean that upgrading from one version of Kunena will result in the loss of messages or attachments; that's not what we're talking about. In this case we are discussing customised changes that you may have made to files located in the ../components/com_kunena/template/default folder (in other words, the place where the Blue Eagle template is installed).

There are two ways that you can implement your own customised CSS changes. One way is to develop your own Kunena template; it's a little complicated and really should only be attempted by medium-to-advanced Joomla users. The second way to to apply any CSS customisations to your Joomla site template CSS file(s). This is by far the easier of the two ways and none of your customised changes will be lost as long as you continue to use the same Joomla site template that you already have.

So, for quick fix changes, yes you can change the Kunena CSS files (and you need to be aware that any changes you make will have to be re-applied when you upgrade from one version of Kunena to the next). For a longer-term solution you need to consider a different approach.

Sozzled, what I've meant with "What is happening is that the upgrade is overwriting the CSS in my own template/folder ..." isn't that the upgrade saved over my files into my own template folder. As you have said, I have already my own folder (../components/com_kunena/template/mytemplate) for my own template and set it as default in the back-end in the template manager. So, these files into this folder weren't overwritten, but the upgrade, in some way, isn't respecting my css style into it. So, what i meant, is that some file in the upgrade, is overwriting the commands in my css files. like (!important), but I've checked the upgrade zipped package file, and there wasn't any .css file that was replaced or overwrite, so I'm wondering which file in 1.6.4 is controlling now the ktop color. as you can see at www.esferadobem.com.br , it's blue and I want brown back. I got to solve the topic titles by adding the !important in the colors that controls the a:link within kunena.forum-min.css, but by applying the same for ktop, the !important didn't solve.

Just by using firebug you can see that you have 2 ktop settings

One is around line 31 the other online 19.

This is where your problem coming from