- Posts: 362
- Thank you received: 45
Kunena 6.3.8 Released
The Kunena team has announce the arrival of Kunena 6.3.8 [K 6.3.8] in stable which is now available for download as a native Joomla extension for J! 4.4.x/5.0.x/5.1.x/5.2.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 and issues discovered during the last development stages of K 6.3
Note: Please go to the Kunena Dashboard after an upgrade so that the Kunena database tables are also updated.
Question Joomla 2.5 and Kunena 1.7.1
Please Log in or Create an account to join the conversation.
Because I have updated my clan page and did not think that the forum could not run.
Please Log in or Create an account to join the conversation.
- Jiminimonka
- Offline
- Elite Member
- YBAS!
Please Log in or Create an account to join the conversation.
So, I contribute this "news" snippet to let members of this community know that Kunena is not the only Joomla extension to be affected by J! 2.5.0. Joomla 2.5.1 is planned for release on Tuesday 31 January.Hi,
If you were following me on Twitter you'd know what's going on. This issue had thrown me into a fit of cursing and swearing
As of Joomla! 2.5.0, the core code relies on the administrator forms having id="adminForm" whereas previous Joomla! versions (1.5, 1.6 and 1.7) relied on the same forms having name="adminForm". Furthermore, Joomla! 1.6 release notes did warn developers that this would happen and urged them to change name="adminForm" to id="adminForm". However, the change was never implemented in the JavaScript supplied with Joomla! 1.6/1.7. If any developer made the suggested change he would find that his component no longer worked with Joomla! 1.5/1.6/1.7 and would have rolled it back. Surprise! Joomla! 2.5.0 includes that change and the components which were working no longer do.
IMHO, the way this change was rolled out caused serious backwards compatibility bug in the Joomla! core. The proper way to roll out such changes is to make the change in the interim releases (1.6, 1.7) and have backwards-compatibility code (an if-block), so that developers can deploy the change over the course of the 12 months of the interim releases. Then, in the stable release (2.5), the backwards compatibility code can be removed. Since this was not the case, Joomla! 2.5 broke our extensions. For my part, I had to re-release every single extension I make to fix this issue.
Unfortunately, this all now comes down to developers having good response times (unlikely, eh?). The have to add both name="adminForm" and id="adminForm" on their administrator forms in order to make them compatible with all current Joomla! versions (1.5, 1.7, 2.5). I suggest starting emailing the developers of your components, letting them know of this issue and the simple necessary workaround. In the mean time, you can open the files of your extensions, look for name="adminForm" and tuck in an id="adminForm" next to it.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
Edit: Alright, I'll try and stay on topic.
Please Log in or Create an account to join the conversation.
I understand people's curiosity, but let's remain on topic. This topic is about problems we're having with K 1.7.x and J! 2.5.Josh wrote: Thanks for the heads up. Now when might we see kunena 2.0? Just curious.
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.