Important KDatabaseQuery naming conflict fatal error

@ johanjanssens:

Of course the conflict must be solved, especially if it breaks administration. It's also very good that you guys reported from the issue now and not after six months, when the damage could have been much larger.

I will try to find time to do it, but please take into consideration of what I've said. As K isn't reserved prefix, using it will likely cause issues like this in the future, too.

Hi Johan,

johanjanssens wrote: In the mean time it looks like we will need to settle with the fact that Kunena 1.6 and Nooku are not compatible.

Yes, this is the case with Kunena 1.6. As Matias mentioned, it was already done this way in Kunena 2.0 (before Stan's post) so it won't be an issue going forward. However, there are over a million downloads of Kunena (not to mention third-party stuff) and it's in pretty wide use compared to Nooku, which is still alpha and only available to developers and partners.

Additionally, we've already announced that an alpha/beta of Kunena 2.0 will be released in Q1 2011. So development is in full swing for that, with effort on Kunena 1.6.x being just bug fixes (Kunena 1.0.x is EOL as of the Q1 release of 2.0). I think Matias is being overly optimistic about "trying" to look into it. We're all tied up with getting 2.0 out and don't realistically have the time. Just don't want to get anyone's hopes up.

Taking into consideration the imbalance of user bases, the likelihood of the Kunena 1.6.x series being around for a while, Nooku still being in alpha, and the lack of prevalence of PHP 5.3 (and moving your code to it to use namespaces), you should change your class names before you reach beta or final. Of course, this is only if Nooku users are using Kunena (and not a Nooku-based product) and are asking for compatibility.

@Matias:

Thanks, there is indeed no easy way around this. Changing our framework prefix from K to Koowa could be an option. Like you we need to acted carefully as we have already quite a lot of code in the wild that is using Nooku Framework.

The 0.7 version is indeed in alpha, but we have a stable 0.5 and 0.6 versions out there that is already widely being used. Changing the prefix would mean all code that is using Nooku Framework would break. That's a major change and something we need to address with care.

Nevertheless I will take this into account and consult with our developer community on how to best address this issue.

It's good to know though that the issue with Kunena will solve itself with the upcoming 2.0 release, also great to hear the beta is due in Q1. Good luck with that. Will keep an eye out for it !

Dear all. What is the status regarding this? I couldn't find any Kunena 2.0 2 beta version. Probably q1 2012 was meant?

Akeeba subscriptions uses Nooku. But since it is still beta, I can probably live without it and there are alternatives.

But Docman will be released soon and also based on Nooku. So probably I won't be able to upgrade Docman (without losing Kunena)?

What is the workaround? Of course I could install jdownloads instead of Docman (jdownloads is really a nice and free download component, but unfortunately doesn't work on joom16).

I also considered the Ninja forum, but it just lacks to many features compared to Kunena (it is still a young component).

The only workaround currently is to find all occurances of KDatabaseQuery from Kunena and do global replace on those. Unfortunately we cannot rename the class easily in K1.6 as it's used in external integration.

Kunena 2.0 is pretty close on beta.

so can be able to run kunena 2.0 to run on nooku server or not