Question Whole site gone down after clicking 'change config'

I think it was change config or update config. I clicked this and whole site has gone down. I can access admin.

Can anyone help, I'm starting to panic

Just to add: All modified file times seem to be in tact so I'm guessing that it's a database entry somewhere triggered by the 'click'

Additionally, I can't access Kunena Admin but can access all other Joomla admin.

Please turn on Joomla debug and look at the error you are getting.

Please share all versions of everything you have installed, maybe a link - as long as the errors are visible.

It is literally impossible to help with no background information.

Sorry, yes it might help

Here's a good start:

500 - JDatabaseMySQL::query: 1146 - Table 'malmesbu_joomla.jos_kunena_config' doesn't exist SQL=SELECT * FROM jos_kunena_config

Additionally, site was running perfectly. All I did was click on 'update config' or 'change config' in Kunena admin and it all went to pot.

OK, found what has caused it, my terminology was slight wrong as it all happened a bit quick.

This is what caused it: I clicked 'default' in Kunena admin which wiped out the kunena config table.

I applied the same table from yesterdays backup and all was fixed.

Phew!

OK. Before other people begin to panic that pressing the Default button will wipe out your entire Kunena configuration and send your website into HTTP 500 Internal Server Error hell, I am going to conduct a scientific test and I'll let you and others know the results.

I can confirm that pressing the Default button on the Kunena configuration panel does not destroy a user's website. I wanted to assure all users that they should have every confidence that they can safely use the Default button on the Kunena configuration panel.

In this one, isolated case, pressing Default button on the Kunena configuration panel may be been responsible - I'm not disputing that - but I am saying that this case represents an unprecedented and extraordinary exception to the general rule. I am pleased to read that, in this user's case, there was a backup plan in place that allowed for the site recovery (just as I, too, made sure that I backed up my site before I tested this facility). It is always a good idea to make a backup before you make any changes to your Joomla configuration, just in case something unexpected happens or in case you make a grave mistake.