Question Remove ALL READ

Hey, Im am trying to remove the "mark all read" button from my index but cant seem to get ride of it. I removed it from fb_category_list_bottom

but its still on the index, any help would be great

thanks in advance

It would help to know what version of Kunena you have installed and what Kunena template you are using. Thanks.

I assume that you are trying to remove one of the "mark all read" buttons, the one that appears at the bottom of the page. Is that correct?

like an idiot, i just noticed i posted this in the wrong section...

im running latest 1.6, and i am talking about the mark all read button below the profile box

*

It wasn't your mistake. You originally posted your request in a K 1.6 category when your question seems to be related to K 1.5. I moved this topic.

There is no fb_category_list_bottom used by K 1.6, that I'm aware of. Where did you see this?

ahhh that would explain why its not working... could that be files left over from 1.5??

Probably

so... err.. any idea how i can edit this on 1.6?? defualt template (same one this site uses)

If you used Firebug for Firefox you would have found (within one minute) that all you need to do is modify the CSS file by adding the line (in red) below:

#Kunena .klist-markallcatsread input.kbutton {
display:none;
margin:4px;
padding:0;
}

I do use firebug, but to be honest i wanted to remove the code not just hide it as I have no use for it within my joomla site..

Thanks for the quick relply tho, I managed to find it now
components/com_kunena/template/default/categories/listcat.php

JOB DONE

As you like - it's your website. It's really better to hide these things than to edit the source code. Editing the source code may save you a millisecond or two but could cost you hours, later, when you need to upgrade to new versions because of other issues. K 1.6.1 is just around the corner (which contains dozens of fixes to K 1.6.0) and you're only going to have to do those changes again. Then there will probably be a K 1.6.2 (and so on) and, again, you're going to have to make those changes. But, like I said, it's your website.