i checked out that in this board the latest posts are shown even for child boards... does anyone have a fix for this bug? (1.1 version, obviously)

This bug really irks me.. I'm gonna try digging through the code later in the morning to see if i can figure it out. I figured maybe it was the upgrade that caused the childboard count to not work.. But i just did a local fresh install of fireboard 1.0.1 n zilch on the child forum count. Is there a config for it? from the backend. Cause i dont think i saw that either. What am i over looking guys?

said i'ld fix it yesterday. Just completed it. i would upload the file but for some reason youc an upload txt files? how odd

child board count fix

I'm sorry.. the permissions on the download section of my site did't allow single file permission settings and i cant set my entire download access to guest... next best thing i can do is just host it in a little dir for you guys

the fix

hope this helps

Brilliant fix Taylor. Many thanks. I simply took your listcat.php file and replaced mine and what do you know, Jed’s a millionaire!

I was wondering if you thought of also editing the code so that on the right hand side it would not show "No Posts" at all in the message board itself in the event it is a message board that contains only child boards?

All of my message boards that contain child boards don't allow posts into the board itself, only into the child boards, so they still show as having "No Posts" at all, which is actually a bit confusing to a user I think if you are showing posts now in the child boards themselves within the message board.

What seems stranger than strange to me is that if you go to the main Fireboard forum page on this site, they have it all working right showing both child board counts as well as the total number of posts in the child boards for the message board itself as well.

I think i am running the latest Fireboard component release, so why I would not get the same result in my forum is beyond me

thank u for Ur work cyberpunk. Iget an mysql error:

Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /var/www/subdomains/alvar.moskitoo/components.../default/listcat.php on line 229

whats that mean... how can i fix it?

I update fb from 1.0.0 to 1.0.1 ... joom 1.0.12

....I dont have "listcat.php"

It must be in your template folder ...


For default template its in:"/components/com_fireboard/template/default/listcat.php"

marcbkk wrote:
Brilliant fix Taylor. Many thanks. I simply took your listcat.php file and replaced mine and what do you know, Jed’s a millionaire!

I was wondering if you thought of also editing the code so that on the right hand side it would not show "No Posts" at all in the message board itself in the event it is a message board that contains only child boards?

All of my message boards that contain child boards don't allow posts into the board itself, only into the child boards, so they still show as having "No Posts" at all, which is actually a bit confusing to a user I think if you are showing posts now in the child boards themselves within the message board.

What seems stranger than strange to me is that if you go to the main Fireboard forum page on this site, they have it all working right showing both child board counts as well as the total number of posts in the child boards for the message board itself as well.

I think i am running the latest Fireboard component release, so why I would not get the same result in my forum is beyond me

welcome. I'm contemplating it. its the same situation for my boards as well. Just haven't approached it as yet. I'll work on the logic for it today and implement by sunday. weekends a bit busy.

bilal wrote:
thank u for Ur work cyberpunk. Iget an mysql error:

Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /var/www/subdomains/alvar.moskitoo/components.../default/listcat.php on line 229

whats that mean... how can i fix it?

I update fb from 1.0.0 to 1.0.1 ... joom 1.0.12

if the loop is supplied an invalid resource it would mean that the previous query failed. which shouldn't be the case. How did you apply the fix? manually or just replacing the file?