So yeah, I really needed this, and I know a lot of other people did too, so I customized listcat.php to fix the problem. I use recursion (it made me feel smart), and I made sure to comment all the stuff I did, but if you have any questions about it, feel free to pm me or shoot me an email or something. Enjoy!

PS - overwrite listcat.php located in /components/com_fireboard/template/default

EDIT: In case anybody isn't exactly sure what I'm posting here, this counts up all the topics and replies in child categories, and gets the latest post by including those child categories as well and displays it on the front page.

EDIT2: This file is the non-optimized version. Look at the next page for my other post with the more optimized file that isn't quite as slow.

Brilliant, it works. You are the man.

Only thing is that Cyberpunk had created a slightly different fix which put post counts next to each of the Chilboard categories, which was handy as well.

Ultimately yours is a better solution, but I thought it would be nice to have both if possible.

So I incorporated Cyberpunk's code into your Listcat file thinking that might work, although it didn't. I guess the code you have added overrides his code.

Anyway, I am attaching the edited Listcat file in which I brought Cyberpunk's code into your file.

Maybe you can have a look and see if there is a way to get both of the fixes working together in one file.

Many thanks again.

ask and ye shall receive. I didn't use any of cyberpunks stuff; it was just easier for me to build off of the method that I was already using. Let me know if you need anything else.

Spot on! I no longer have words to describe how good you are. I think this is the most significant fix to this extension made so far and was the biggest Achilles heel in my whole site. Now case closed. Many many thanks!

You should really have a gold medal for this!!
Works great and implemented just as I wanted it to look... Thanks!!!



I still think it is strange since this is a community project that it has been coded on this site but this modification is "secret" or unpublished. I just think that it is unneccessary for people to work on fixes that apparently already have been fixed.

But once again, thanks for a really good job!!

Absolutely strange to me too. The developers upload the latest version of the fireboard extension to the site we are communicating on, which has that function implemented, but in the version made available for public download they don't include it. I don't know what the issue is or the reason is, but it is such a standard thing in forums. SMF, which I am running on another forum has had it for at least a couple of years already. And I don't see it is a special function that they would hold back for any reason. Well, I think I am done scratching my head and again a special thanks and best wishes goes out to Philman for taking the time to write a fix for it and make it available for all of us to use.

Great stuff phil.. I"ve been really busy with some Projects and i haven't had time to do much opensource community development. Congrats on your fix. you da man.

This fix is really great!!!! I have another problem and I wonder if this patch broke the recent post plugin. I have not had any updates to the recent posts plugin (at the bottom of the forum) since yesterday (8/14) even though there have been posts today.

Thanks for any ideas you may have!

I have noticed on the site where I am running your patch that it takes several (5-8) seconds for the forum to appear. I wonder if that is due to the processing to count up the messages and replies. As the forum becomes more active do you anticipate that the delay could be even longer?

Thanks again!

Actually I have the same problem. I didn't notice at first but it is true, it really makes the page to load really slow. Is there a way to make the code a little nicer? I have not looked at the code but I will try to have a look at it tonight.

Maybe there are many more DB-requests involved to get this functionality? The final result is great so now we only have some code optimization to do... Would not be too hard I hope