Kunena 7.0.4 Released

The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 7.0

This category contains miscellaneous, uncategorised third-party extensions (e.g. JomSocial, Community Builder, etc.) relating to older versions of Kunena that are no longer supported.

This category may also contain a few topics relating to K 1.6 that may have been moved here possibly by mistake.

The topics in this category are for historical interest only. Owing to the structural differences between K 1.6 and K 1.7, the ideas in these topics may not work with later versions and, for that reason, the topics are locked.

Question [Merged topic] K 1.6 needs "autodetect" for integration with JomSocial

More
15 years 9 months ago - 15 years 9 months ago #55739 by mindriot
Just did an upgrade from K1.5.9 to K1.6 RC1 on a Joomla 1.5.20 site.

Process went without problems.

I recreated all the main menu links but whenever I select any of them I get blank pages.

With debugging on nothing came to light but when I set error reporting to maximum I get this :

Fatal error: Call to a member function getAllowedCategories() on a non-object in /home/safnet/public_html/components/com_kunena/class.kunena.php on line 517

Heres the output from report configuration settings :

This message contains confidential information

Database collation check: The collation of your table fields are correct

Legacy mode: Disabled | Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 2000 seconds | Max execution memory: 128M | Max file upload: 64M

Kunena version detailled: Installed version: 1.6.0-RC1 | Build: 3173 | Version name: Kujadili | Kunena detailled configuration:

Warning: Spoiler!

Last edit: 15 years 9 months ago by sozzled. Reason: Merged from several discussion; changed subject to improve search relevance

Please Log in or Create an account to join the conversation.

More
15 years 9 months ago #55745 by fxstein
What is your jomsocial version on that server? You could try disabling jomsocial integration to see if the pages render.

You should see errors in the apache error log.

We love stars on the Joomla Extension Directory . :-)

Please Log in or Create an account to join the conversation.

More
15 years 9 months ago #55750 by mindriot
Thanks for the reply.

Ive got JS uninstalled right now to do the horrible upgrade process it requires every time theres a new version, I had 1.6.289 but I am planning to go to 1.8.7

Could it be this that is the cause? (uninstalled just now)

Please Log in or Create an account to join the conversation.

More
15 years 9 months ago #55752 by mindriot
I just looked through config again, it had retained Jomsocial specific selections for some of the integration settings :)

Switched to autodetect and its happy, many thanks for the clue.
The following user(s) said Thank You: sozzled

Please Log in or Create an account to join the conversation.

More
15 years 9 months ago #55753 by sozzled
I think this is important enough to make a sticky topic for the Jomsocial category! Thanks very much for reporting the matter.

Please Log in or Create an account to join the conversation.

More
15 years 9 months ago - 15 years 9 months ago #55755 by mindriot
No probs, I googled "com_kunena/class.kunena.php on line 517" and saw results for a number of sites that seem to report the error so I reckon Im not the only one to hit this.

Im not sure that autodetect is needed for JS, its more at the time I encountered the error and posted the integration settings in my Kunena had retained the previous "Jomsocial" specific settings from my Kunena 1.5.9 install when I had Jomsocial 1.6.289 uninstalled in preperation to reinstall 1.8.7, I merely switched to "Autodetect" and found that reverted Kunena to using its own system in the abscence of Jomsocial.

Further, now Ive just reinstalled JS 1.8.7 Kunena has now switched from its on system back to using the JS information while the integration settings are still set to "autodetect".

Happy to have helped :)
Last edit: 15 years 9 months ago by mindriot.

Please Log in or Create an account to join the conversation.

Time to create page: 0.250 seconds