Third party template developers blamed for problems caused by Kunena team
Another unannounced (and apparently untested) change was made in Kunena 4.0.5 [K 4.0.5] that affects everyone who uses J! 3.4. The change is embarrassing for me, personally, and for everyone who designs and sells Kunena templates. The problem is: people use K 4.0.5 with J! 3.4 will not be able to install other forum templates!
I am not sure what was the rationale behind the change in K 4.0.5—very few changes made by the Kunena team are well-explained these days—but apparently the developers were aware of an issue about three months ago that affected the ability to install the Crypsis template with J! 3.4.2.
We know the Kunena team is attempting to regain their reputation after continuing failures with each successive release of K 4.0 and their inability to penetrate the market with their new template. Community take-up of Crypsis has been slow (almost non-existent) with more than 9 out of 10 users opting to use the Blue Eagle version of K 4.0 (if we use the configuration reports posted at the Kunena forum site as any indication).
I wasn’t aware of this particular issue until I attempted to install the new Crypsis B3 (beta) template on a K 4.0.5 (J! 3.4.4) test site. Note the developer’s response in the discussion we had:
This is a know[n] issue, and has been fixed. The installer has changed in Joomla 3.4.4.Jelle Kok, Kunena 4.0.5 bug (Subscriptions), 13-Sep-2015
What complete nonsense! The issue was “known” three months ago—long before the release of J! 3.4.4—and the [Kunena template] “installer” was “changed” for K 4.0.4/5. When the issue was first reported, the developers claimed to have fixed the problem that affected people installing Crypsis. Not only have the developers failed to fix the issues with installing Crypsis, they have now made it virtually impossible for people to install any other template with K 4.0.5. For those of us who offer Kunena templates for sale, this is extremely disturbing news. People will naturally accuse third-party developers of misrepresentation when the templates they’ve purchased will not install. The fault is not with the Kunena template; the fault is in the Kunena core.
The problem was caused by the Kunena development team. The problems cannot be cured because the developers will not take the community into their confidence; they will not explain what is happening, why things are happening and their plans for the future of Kunena. Instead it is left to independent commentators like me to try to explain to ordinary users what’s happening; it’s not easy when we have little publicly-available information to work with.
There’s little doubt in my mind that the developers don’t care what happens to third-party designers as long as Crypsis eventually dominates the market. The specific problem I’ve referred to may be corrected in the next release of Kunena but questions remain about new problems that will be introduced in K 4.0.6. It is because of the increasing instability of Kunena that I refrained from installing K 4.0.5 on any of my production websites; there have been far too many reported problems for me to jeopardise my business. Every new release of K 4.0 introduces untested new features.
Perhaps the best way of demonstrating this claim is to look at the Kunena website. Is it any wonder that the Kunena development team is unable to properly test their product while the website operates on an unsupported version of Joomla? Why would people want to use Crypsis when the development team cannot stand behind their product and show us what it looks like and how it works in a truly production environment? I will have more to write about this in another article but, for the time being, it is more important that we find out when the errors will be fixed.
K 4.0.5 was released (after the abortive K 4.0.4) on 16 August [this year]—more than one month ago. K 4.0.6 may or may not be ready for release; the developers have gone back to playing their “secret squirrel” games, so we really have no way of knowing what their plans may be. If my criticisms are unfounded, I will be the first to admit my faults. The Kunena team are well aware of my criticisms (they visit this website on a regular basis) and they’ve tried to silence me in various ways. If I am wrong then let’s hear from the other side; let’s see the narrative from the development team’s perspective. It’s in their interests to put their side of the case; that’s all I’m really trying to do here: get to the truth.
The bottom-line is that the technical problem I’ve referred to in this article has been fixed (as long as you replace one of the files in Kunena with the new version available from GitHub). The ongoing management problems within the Kunena team remain, lack of adequate documents, failure to engage properly with the community, etc., these other problems remain unresolved and getting worse.
