We are setting up Kunena ahead of a migration. When I log in with my site administrator account, I receive the following error:
Rendering Error in layout Widget/Module: Call to a member function cachedCompile() on null. Please enable debug mode for more information.
With debugging turned on, as suggested, the full error message is:
Rendering Error in layout Widget/Module: Call to a member function cachedCompile() on null in /var/www/vhosts/transalpclub.nl/kunena.transalpclub.nl/plugins/system/helix3/core/helix3.php on line 774
Layout was rendered in /var/www/vhosts/transalpclub.nl/kunena.transalpclub.nl/components/com_kunena/template/crypsisb3/layouts/page/default.php on line 25
helix3.php line 774 (-->):
public static function addLess($less, $css, $attribs = array())
$template = JFactory::getApplication()->getTemplate();
$themepath = JPATH_THEMES . '/' . $template;
if (self::getParam('lessoption') and self::getParam('lessoption') == '1')
if (file_exists($themepath . "/less/" . $less . ".less"))
--> self::getInstance()->autoCompileLess($themepath . "/less/" . $less . ".less", $themepath . "/css/" . $css . ".css");
self::getInstance()->addCSS($css . '.css', $attribs);
default.php line 25 (-->):
--> echo $this->subLayout('Widget/Module')->set('position', 'kunena_top');
The if statement is inside a block starting with:
<div id="kunena" class="layout <?php echo $this->options->get('pageclass_sfx'); ?>">
The module is published in the kunena_top position.
I haven't got a clue where to start looking. With a normal, non-privileged, account the module works fine.
Any help would be appreciated.
I don't think this issue has anything to do with JFBConnect or our SCLogin module. It sounds like an issue with Kunena or your template, but I'm unsure what. I'd recommend you contact either of those developers to hopefully help you narrow down the issue further and get things going.
If there is a reason you think our extensions are causing this issue, definitely let us know and we'll help however we can.
Thanks. I'll ask the the other parties. It kinda makes sense, seeing that their code is mentioned in the error message.
I'll let you know of their findings. It may safe other people coming across this issue some time.
Sounds good, and keep us posted. Again, if you think it's related to anything with our extensions, just let us know what you're using (SCLogin or JFBConnect or both) and what versions.
Together with help from Kunena and JoomDev we determined that the issue is in the template we have in use. We were unable, however, to reproduce the issue and/or determine its cause.
For us it's minor since super users will not log in to the frontend of the forum. Case closed.