- Posts: 7329
- Thank you received: 1434
Kunena 6.3.7 Released
The Kunena team has announce the arrival of Kunena 6.3.7 [K 6.3.7] 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.
Merged Sorry, installation failed with following error: {"success":true,"status":"33%","current":"Prepare Installation","log":"\n\t\n\t\t Prepare Installation\n\t\t \n\t\t... OK\n\t\t \n\t\n\t\n"}
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.
Please Log in or Create an account to join the conversation.
*** Topics merged ***
Blue Eagle vs. Crypsis reference guide
Read my blog and
Please Log in or Create an account to join the conversation.
go to Plugins admin
desactivate all plugins
install Kunena from web
Re-activate the plugins
to me it has worked for me
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Operating System : Arch Linux
Joomla Version : 3.3.0
PHP Version : 5.5.12-1
MySQL (MariaDB) Version : 5.5.37
I have no log entries to reflect any sort of error and have 100% made sure all the environment requirements are met.
If I unpack the package file and install the Kunena "pieces" individually, there is no problem but, there is also no available menu, I presume because the <customfiles> part of the initial schema file isn't called containing:
If I run that initial schema file through a tool like XML Lint, it reports no less than 48 errors. Because I need to use Kunena forums, I will investigate further but until that moment, this post just serves for some food for thought and error verification.
Kind regards
Please Log in or Create an account to join the conversation.
Ongoing investigation
Please Log in or Create an account to join the conversation.
Out of pure speculation (because I notice you have been telling people to disable all their plugins) the error wouldn't have anything to do with the slow migration of the Joomla backend over to jQuery would it?
What (for the moment) baffles me is that if I place a console.log() straight after the following callbacks from Request.JSON, it never fires.
Please Log in or Create an account to join the conversation.
{"success":true,"status":"33%","current":"Prepare Installation","log":"<table>\n\t<tr>\n\t\t<td>Prepare Installation<\/td>\n\t\t<td style=\"color: green\">\n\t\t... OK<\/td>\n\t\t<td><\/td>\n\t<\/tr>\n\t<\/table>\n"}
It is JS conflict in mootools-core.js (line 164)
How I can to solve this
Please Log in or Create an account to join the conversation.