Question [Resolved] Upgrading to 1.6.5 "not possible to delete xxx.php"

Thanks 810 ... all permissions are writeable
also checked files listed in the report and they are set to 0777.
As mentioned, the forum (Currently broken & off line) has so few posts, I could wipe the lot without an issue.
But the system won't even allow me to do that.

Have access to CPanel, MyPHP, and site Admin.
If none of these enable me to remove, delete and re-install the latest Rev, I will endevour to contact my Site developer and get back up the priority list.

(My issue... I'm learning, with too much access and maybe too little knowlege)

As a general rule no file should be set to 777 which gives read write execute to not only the owner but Group and Other as well. As a general rule folders should be 755, files should be 644

I do appologise for resurrecting this thread in relation to my Kunena installation.
I have not been able to resolve this issue no matter what I try.

I have un-installed Ver: 1.5.4
and whatever I try to install after this, I just get:

It was not possible to copy the selected file.
JInstaller::install: Failed to copy file: /home/xxxxx/public_html/tmp/install_4ede705bacf8c/com_kunena_v1.7.0_b5135_2011-08-29[1]/api.php to /home/xxxxx/public_html/administrator/components/com_kunena/api.php
It was not possible to delete the selected file.: 'COPYRIGHT.php'
It was not possible to delete the selected file.: 'CHANGELOG.php'
It was not possible to delete the selected file.: 'router.php'
It was not possible to delete the selected file.: 'kunena.php'

I have gone to the C-Panel and deleted the files listed.
I've even deleted any folders referencing Com_Kunena under Administration/Components/ and Public_html/Components/

Still no use, and whenever I revisit the C_Panel all the additional files that I deleted are back again dated with the original install date of 2009
and I can't find api.php anywhere.

I don't need any details or reference from the orig set up, but I can't even start from scratch. All permissions are OK and writeable.
Last chance or no forum ... its just annoying me now.

Matias wrote (in msg #2) that these error messages point to a folder/file permissions issue. I agree with him. 810 also provided the same advice.

It seems, from your last message, that you are trying to install K 1.7.0. Please don't use that version. K 1.7.1 has been available for nearly one month.

I would not be waiting 2 months for an answer, if this was my website. I would be doing everything possible to resolve the problem as soon as possible or (as you say) go elsewhere and look for a different solution.

It takes less than one hour to create a Joomla website and less than 2 minutes to install Kunena and, in 99% of all cases, if you follow the recommended approach, everything works without having to make a single change to anything. But, like all good buildings, if the foundations are bad your site will crash. I strongly recommend that you very carefully read K 1.6 and K 1.7 Upgrade Guide ... and I hope that some of this information helps you.

Thanks,
I've read everything that I could find inc installation guidelines and followed them to the letter.
I did not set up the site (I have been unable to get the developer to assist to date, hence the delay).
All revs tried inc 1.7.1. Un-install/Install/upgrade/fresh ... same error

I see Com_Kunena in both public_html/components/ and also in public_html/Admin/Components

ini.php is in public_html, not in Admin/components/Com_Kunena,
Copyright, changelog etc is in public_html/components/Com_Kunena - NOT in Admin/...
All files are green and writeable.

All permissions seem OK, so either they are mixed across public_html/Components/Com_Kunna and public_html/Admin/Components folder and there is some code that refers to relevant files located elsewhere that Kunena install require to be in a specific location.
or my own Super Admin is not super enough.

Manual removal of files reverts on refresh.
I shall go find the developer again and see if I can persuade him to divert his attention from more pressing requirements, but last call suggested that no reason why it shouldnt work.

Thanks.

All folder and file permissions in your Joomla folder (and recursively through your site) should be set the same (as recommended by Joomla) and your files should be owned by Apache:Apache. If you have mixed permissions, this may account for why you're having problems.