Question My Discussions Board not showing correctly

... and I also need to distance myself from the developers. The opinions I wrote were mine and had you read the entire discussion (that I referenced) you would undestand that my opinions were not shared by the developers.

However, unless someone is willing to correct me, the statements I've made about "installing alpha test versions [of any software] at your own risk" are, in my opinion, entirely correct even if they're not sympathetic.

I wrote Never again publicly release alpha test version precisely to avoid the argument that you have raised ... or at least to offer feedback to the development team about the risks they may take in the future by repeating this experience.

When I wrote "People are dumb" in the Never again publicly release alpha test version discussion - and I've been roundly criticised for that uncharitable turn-of-phrase - I think it's important put things in their full context

I would like to say this in a less abrasive way but ... people are dumb! The simple truth is that "ordinary users" - if you understand my meaning - cannot be trusted to use to test versions of new products in a responsible manner. I hope the development team learns from this exercise: never again publicly release an alpha test version. Keep alpha test in quarantine. Only allow a limited number of trusted users to participate in the alpha testing. In this way it will save the developers' time and it will save "ordinary users", like me, time too.

Basically, what I was trying to explain (putting it in less severe terms) is that, in general, people don't understand their responsibilities with alpha release of software.

I cannot say for certain, that the problems you now have with Kunena 1.0.9 were the direct result of installing Kunena 1.5.0a in the first place. I said there is sufficient anecdoctal evidence at www.kunena.com to support claims made by others that this was their experience. I can also say, from my observations, that they had some difficulty untangling the mess they got themselves into. For example, people had to DROP certain Kunena-related SQL tables. In some cases they were able to successfully recover and proceed without having to re-install Joomla. But I must add that I cannot properly advise whether DROPping SQL tables is appropriate to your particular circumstances.

Maybe one of the developers would like to take your case on board. In the meantime, I suggest you search the forums for clues on what options you might have.

There is a known bug in Kunena 1.0.9 which looks just like this. This is how to fix it:

Add global $database; as the first line of function MySQLVersion() in components/com_kunena/lib/kunena.version.php :

We are sorry that you got error messages that should not have been there. Currently we don't have enough active people to test our new builds and bugs slip into releases. We are trying hard to fix that and to test the product better.