Question K 3.0.0 b3: Uncaught exception 'RuntimeException' with message 'Library path __DIR__ cannot be found.' in ../libraries/loader.php:251

After restoring my website using Plesk I can not not restart my Joomla website anymore. I get a Fatal error:

Fatal error: Uncaught exception 'RuntimeException' with message 'Library path __DIR__ cannot be found.' in
/var/www/vhosts/derodekaters.nl/httpdocs/libraries/loader.php:251 Stack trace: #0
/var/www/vhosts/derodekaters.nl/httpdocs/libraries/kunena/bootstrap.php(19): JLoader::registerPrefix('Kunena', '__DIR__') #1
/var/www/vhosts/derodekaters.nl/httpdocs/administrator/components/com_kunena/api.php(38): require_once('/var/www/vhosts...') #2
/var/www/vhosts/derodekaters.nl/httpdocs/plugins/system/kunena/kunena.php(28): require_once('/var/www/vhosts...') #3
/var/www/vhosts/derodekaters.nl/httpdocs/libraries/joomla/plugin/helper.php(194): plgSystemKunena->__construct(Object(JDispatcher), Array) #4
/var/www/vhosts/derodekaters.nl/httpdocs/libraries/joomla/plugin/helper.php(125): JPluginHelper::_import(Object(stdClass), true, NULL) #5
/var/www/vhosts/derodekaters.nl/httpdocs/libraries/joomla/application/application.php(229): JPluginHelper::importPlugin('system') #6
/var/www/vhosts/derodekaters.nl/httpdocs/includes/application.php in /var/www/vhosts/derodekaters.nl/httpdocs/libraries/loader.php on line 251

Is it posssible that the problem is caused by Kunena?
I use Joomla 2.5.7

And this issue relates to K 3.0.1, yes?

It would have been so nice if we could have seen your K 3.0.1 configuration report but, as you say, your entire Joomla website has gone pear-shaped? It does not look like the issue (i.e. you cannot restart your Joomla website any more) is related to Kunena, necessarily, unless you are similarly getting similar errors with your Joomla backend. You can get to the Joomla backend?

Unfortunately I also cannot get access to the backend anymore. It results in the same errors..

sozzled wrote: And this issue relates to K 3.0.1, yes?

It would have been so nice if we could have seen your K 3.0.1 configuration report but, as you say, your entire Joomla website has gone pear-shaped? It does not look like the issue (i.e. you cannot restart your Joomla website any more) is related to Kunena, necessarily, unless you are similarly getting similar errors with your Joomla backend. You can get to the Joomla backend?

Well, we haven't really got time to sit around and wonder if this situation was caused by Kunena or not (but the trace-back shows that Kunena is involved in some way).

You still have not informed us if this situation involved K 3.0.1 or some other version of Kunena.

These questions, while of some academic interest, are not useful in terms of the main objective which is to re-establish your website on the internet. My advice is to use a backup of your website made before all of these problems occurred.

I have no experience or familiarity with Plesk (and I cannot help you there). I do not even understand the reason that prompted you to "restore your site" in the first place. I can only wish you good luck and hope that you find a way to recover your site from the mess it has become. I wish I could tell you, for certain, if the problem is related specifically to the Kunena installation on your website but, I know very little about the error message you're getting unless I spend a couple of hours searching the internet and the Joomla discussion forum to see if someone else has been in the same boat as you. And you don't want to sit around doing nothing while I track this down, do you?

Sorry. I've not seen this before.

The version I use is pkg_kunena_v3.0.0-BETA3_2013-04-19

No wonder you were having problems! :ohmy: I believe that we made every effort to advise people that beta releases could not be guaranteed and that people should be extremely cautious if they install beta release of any software on their production website.

We do not offer support for beta software. No-one offers support involving beta software. Beta software always comes with the "you accept all risks and responsibilities for any failures that may occur, or damage to normal operations, if you use this software".

So, now we have a new problem.

Best suggestion I have: go back to a reliable backup of your website, and use K 3.0.1

There is no support issue here that I can tell. K 3.0.0 Beta 3 was three public releases ago.