[wp-hackers] Uninstall Handling

Muro, Matthew mmuro at advance.ua.edu
Sat Apr 9 13:45:17 UTC 2011


One idea is that you could create your own uninstall procedure that's manually run from a plugin settings page that simply runs delete_option.  If you have to manually delete the plugin anyways, this shouldn't be too much of a stretch.

Matthew Muro

On Apr 9, 2011, at 7:00 AM, <wp-hackers-request at lists.automattic.com<mailto:wp-hackers-request at lists.automattic.com>> <wp-hackers-request at lists.automattic.com<mailto:wp-hackers-request at lists.automattic.com>> wrote:

Message: 2
Date: Sat, 9 Apr 2011 06:39:53 -0500
From: Ken Brucker <Ken at pumastudios.com<mailto:Ken at pumastudios.com>>
Subject: Re: [wp-hackers] Uninstall Handling
To: wp-hackers at lists.automattic.com<mailto:wp-hackers at lists.automattic.com>
Message-ID: <1199EB39-3954-48DF-9AE6-9D373150A341 at pumastudios.com<mailto:1199EB39-3954-48DF-9AE6-9D373150A341 at pumastudios.com>>
Content-Type: text/plain; charset=windows-1252

Dion,

I am trying to use the uninstall hook.  However, unless you provide valid FTP/sFTP login credentials you can't get to the point of executing the hook.  In my situation, FTP/sFTP are not enabled on the server so there's no way to respond in a way that will allow the uninstall hook to execute.

What I need is a method to execute the uninstall hook WITHOUT the requirement to provide the FTP/sFTP credentials.  As I mentioned before, I consider this to be a design flaw as I'm unable to trigger the plugin uninstall code.

It's not a requirement that plugins be installed using the Admin screen, why should it be a requirement that they be deleted (i.e. remove the files) through it?



More information about the wp-hackers mailing list