Solved Installation error - Unable to create destination

Now, things can get a little complicated when we start talking about shared Web Servers, the Web Server software will be running with its own username and groupname, most servers are configured for them to use either "apache" and "apache" or "nobody" and "nobody" as username and groupname. Here is the problem. Your Web Server runs as its own user, and this user is not you or in your group, so the first two sets of permissions do not apply to it. Only the world (other) permissions apply. Therefore, if you configure a permissions set similar to 640 on your website files, your Web Server will not be able to run your website files.

docs.joomla.org/How_do_UNIX_file_permissions_work%3F

Good to know I'm not the only one then.

According to "Joomla Directory Permission" I have everything WRITABLE, except for "configuration.php" file

Funesto wrote: Same problem I have in my thread ...

Although I am a little sceptical when people make the claim "I have the same problem" , for your sake I have merged the two topics together in the hope that, perhaps, you will both be able to help each other with this "same problem".

General information about folder/file ownership/permissions is given in the Wiki article Securing Kunena . The information in this article is obtained from Joomla.

Please understand, this is not specifically a Kunena problem. This is a problem relating to website administration.

I recommend you guys to take a look of your server provider... personally, I recommend you guys CGI or FastCGI server providors, it's so simple!

docs.joomla.org/Security_Checklist/Hosting_and_Server_Setup
docs.joomla.org/Security_and_Performance..._hosting_provider.3F

These are things, what is NOT Kunena things, but Kunena is Securing too that and you cannot blame us! I think...

sozzled wrote:
Please understand, this is not specifically a Kunena problem. This is a problem relating to website administration.

Could it be a problem with the Kunena installation files? What if I were to unpack the main zip and put all the folders within the package file into the correct libraries/components/media/plugin directories and go to discover instead in the extension installation menu?