By kneep on

Don't panic, don't want to stop using Drupal.

I've got an "old" Drupal6 site that needs a complete make-over, and has a lot of legacy: not correctly uninstalled modules, files in protected directories I can't remove, some small bugs, wrong theme, et cetera. The association that owns the site will change it's style and structure, so the style and content of the website needs to be changed completely too.
I want to uninstall the Drupal 6 version and to install a new Drupal 7 version.

Uninstalling modules and removing most files and the database is not the issue. The problem lies with the files and directories that are by Apache. Couldn't find the solution in the forum or the documentation.

How to uninstall the site completely, so that all files that are owned by Apache are removed too?

Robert

⋅ Categories: Drupal 6.x

Comments

jaypan’s picture

jaypan
Location Victoria, BC
commented

What do you mean by 'uninstall'? Drupal isn't uninstalled, it is deleted. If you want to delete Drupal, delete the file system, delete the database. But I don't think that really answers your question, so please give some more information.

Contact me to contract me for D7 -> D10/11 migrations.

kneep’s picture

kneep commented

You're right, I just want to remove files. Not only former Drupal-files, but also some from Fengoffice. I managed thanks to the answers I received here.

dman’s picture

dman commented

Perhaps you are asking how to Change permissions on webserver-owned files so that you can work with them yourself

.dan. is the New Zealand Drupal Developer working on Government Web Standards

mylocaltrades’s picture

mylocaltrades commented

Or perhaps you need to chmod the files that do not remove from your control panel file manager?

Offering Drupal website services to the UK - www.my-local-trades.co.uk

kneep’s picture

kneep commented

Indeed, chmod would be better, as the fix.php seems to have some side-effects in case I don't want to remove the whole site. Via FTP I can't chmod files with owner 48 48, files that are generated by Drupal-modules.
But at least now I have a good method to remove "resistant" files after deinstalling Drupal and other systems. Not it will happen often, as I'm using Drupal for almost site.

kneep’s picture

kneep commented

Thanks for the help. I tried Take Control before, but somehow I never could get it working.

Fix.php did the job. I also tried on an inactive website in a sub-domain: it did what it had to do, but when I tried to reverse it by changing the chmod in the script to 755, Drupal complained it couldn't access the files no longer. Didn't matter, as the site was only in use as a test site anyway. No harm done.

Thanks for your help.