Sticky [Resolved] Fatal error: Call to a member function authorisedLevels() on a non-object in /administrator/components/com_kunena/libraries/integration/joomla16/access.php on line 57

It turns out there was an error in php.ini

The call to load the curl dll for windows systems had been uncommented, and naturally being a centos/cpanel server it wasnt finding it. This didnt seem to bother joomla or other extensions but it caused kunena to throw a fit.

Once commented out and the necessary items restarted everything appears to be fine.

Still getting 500 error on K1.7.2 on Joomla 1.5.25 site but nothing at all being reported in errors and nothing being fed into error logs :S

Happens when trying to view a thread :

pbmcltd.com/General-Discussion/21-Leading-Indicators.html

Hi - seems you found a solution as the link to the post, you published in your last mail, works. What was your solution?

I have the same issue. Using Joomla 2.5.1, Kunena 1.7.2. All of a sudden I get this error message: Fatal error: Call to a member function authorisedLevels() on a non-object in /administrator/components/com_kunena/libraries/integration/joomla16/access.php on line 57

Thx!

Hi, the Joomla 1.5 site came good after a short while but not immediately for some odd reason, whereas the fix resulted in the immediate rectification of the problem on the Joomla 2.5 site.

The cause of the problem was simple, a call to a curl dll line was uncommented in php, the call is only necessary on windows systems.

To clarify my server runs CentOS with WHM and CPanel, on linux the call for the dll isnt required (yet it caused upset to kunena). Further, my server runs Apache with SUphp, and I have it set to allow local php.ini files for my own individual sites. Somehow, probably my own fault, Id managed to uncomment the line in my master php.ini before I copied it to make local php.ini copies. These config files are hellishly sensetive to syntax and spelling, one tiny mistake can punish you, even simply using the wrong editor.

This was the line :

and this is waht it should be on my type of server :

The preceding semi-colon is a comment, it comments out the line, effectively telling apache to ignore the line.

I have full access to everything as the entire server is mine (fully managed provider), however if youre hosted you probably wont have access to php.ini, and possibly not the ability to use local php.ini over-ride files, it depends what handler your server is configured to use for apache (causes different functionality), or indeed if its apache at all or a windows server using IIS

If you are using a shared hosting account you should pursue this with your hosting provider if youre sure its nothing directly related to your actions.

Mindriot, thank you for your extensive reply. Just looked at my site - it is working again. I dont understand the logic behind it - how is this possible? I didnt change anything.

My site is hosted by 1&1 Germany, probably the admin changed something and rechanged it last night...

As far as I understood, the problem was related to CURL. And you disabled CURL, then Kunena worked again.

Well, if I disable CURL, then I think have a problem with my SobiPro component, as it is requiring CURL as far as I remember.

Anyway - lets see if this occurs again. Thanks!

Hi, no probs, its possible it was a temporary fault or misconfiguration on your server. I think you may have partly misunderstood me, to clarify my system is fully enabled to use curl, it is a good thing to have, my error was simply just a wrong call to enable a windows dll in the apache configuration that broke a linux system. Curl was already functional before the error and remained so afterward.

Often hosts will correct a fault or problem without reporting it to end users, it really depends on the attitude and ethos of the company, and its possible the admins may not have been aware there was an issue that troubled end users. You should keep curl enabled.

As before I think you should make enquiries of your host, even though the problems seems rectified for now it is a good thing to have a better understanding of what happened for future issues.

I use Kunena 1.7.2 on Joomla 2.5.1 and I also got the 500 Internal Server Error and in my PHP error log had the associated error:

PHP Fatal error: Call to a member function authorisedLevels() on a non-object in /administrator/components/com_kunena/libraries/integration/joomla16/access.php on line 57

I found the error occurred after waking my computer from sleep. With the web browser still open to the Kunena "Recent Topics" page I went to reload the page and got the 500 error. I hypothesize this has something to do with trying to reload the page with the original session long expired. Loading a different web browser on my computer, the page loaded with no error.

In the file mentioned in the PHP error log (/administrator/components/com_kunena/libraries/integration/joomla16/access.php) on line 55 it turned out $user was being set to null, which led to the error on line 57.

My solution was to put the following PHP code on line 56 to force the Joomla session to restart:

The error ought to go away without this fix if you restart your web browser, or if you log out of and into Joomla again.