Would be interesting to know exactly the root cause, as reinstalling is ok on local but not on production sites.
Has a bug report been opened in the bug traker for this bug in 1.0.4 ?

From my first search it seems this bug hasn't been filled yet in the bug tracker, it would be interesting if we could fill all together a detailed description of this bug.
I will try to dig on this and find what cause the problem on my install.

Would that count as a "bug"? The discrepancy/ies has/have been known of since the .4 release but it is unknown as to what the discrepancies are.

I did the reinstall on a live site with no issues since the database is never touched. Applied this SVN patch and have had no problems. I even updated the JQuery to the latest version for good measure.

I would urge everyone to not use the .4 upgrade patch files and just do a full reinstall (NOT a CLEAN INSTALL) and apply THIS patch after you have tested it out first. Of course BACKUP BACKUP BACKUP first.

Hum, i would rather report the bug in the patch files which create this side effect error has this would help to fix the patch files. Most of users won't come here and read your advice and so far it is the only problem i met with the patch files, in addition you should detail more explicitly what you call a full reinstall. In my mind reinstall goes along with image and template directory loss where it becomes annoying when you installed a custom template in which you did css modifications.

I mean if this is a recurrent problem a tutorial about performing what you call a full reinstall would help especially if linked in the wiki.

That is exactly what I mean by full reinstall. Backup anything you want to save (template folders, images, etc) uninstall FB, reinstall FB and reupload anything that was deleted by the uninstall. If you are unsure backup all your FB folders in their entirety.

I don't see a need for A tutorial.

Anyway this is a dirty workaround not a solution and may be a real pain for big sites, patch files are supposed to work and is what most users will use. As i said most users won't come here and eventually read your advice so most users may still have this issue if no one care to fix the patch files so advising this is good as a temp fix but not in the long run. That's why i'm more interested in finding what is wrong in the patch file package and fill the suitable bug report so that patch files package can be fixed and most users not impacted by this bug.

Keep in mind that most users won't browse the forum and they won't benefit your temp workaround so fixing the patch files is important and inescapable IMO. I'm not fine with letting fireboard 1.0.4 patch file users alone with their issues.

Will start digging on this.

Now for that I have some good news. I am working on a re-write of the install/upgrade procedure with the target being there can only be one package. No patch vs full install. No more manual SQL scripts. Uninstall Fireboard and reinstall the new version.
Far too many problems with the complicated upgrades...

Good news indeed! I knew you hinted about it recently. Now for the onslaught of "Is it ready yet?" questions.

zachheise wrote:
grumblemarc wrote:
Maybe it's Joomla template related like you said? We would need people to start reporting that info if they are having this scrollbar problem.

Sure, I'm using the standard "default" fireboard template (the older blue one) and the rhuk joomla template. Nothing has been altered except language files on fireboard, and I haven't made any substantive changes whatsoever to the rhuk template - just simple things like colors, images, etc.

Please let me know if there's anything else I can do to help out, information-wise.

Where do I find the rhuk template? I need to try that out.

grumblemarc wrote:
Good news indeed! I knew you hinted about it recently. Now for the onslaught of "Is it ready yet?" questions.

It will be ready for testing soon...

It's the Solarflare template. Rhuk (RocketThemes) is the author.