[wp-hackers] register_uninstall_hook VS uninstall.php

Davit Barbakadze jayarjo at gmail.com
Sat May 8 19:30:36 UTC 2010

I'm not going to use it for something else. I described my problem above. It
is that I use variables in options and table names, and it would be a
duplicate work to redefine the whole logic in uninstall.php. I just do not
see a point why I shouldn't be able to use the logic I already have (and use
OOP approach and not that ugly function namespacing). And then there is some
support built-in already, like calling callback with an action instead of
calling it in some other way. Why not to make this support more conssistent
and convenient.

On Sat, May 8, 2010 at 10:55 PM, Andrew Nacin <wp at andrewnacin.com> wrote:

> On Sat, May 8, 2010 at 2:43 PM, Davit Barbakadze <jayarjo at gmail.com>
> wrote:
> > Well, thanks :) Although I think that's the case when an API is faulty
> and
> > needs some improvement. Is it so hard to remove WP_UNINSTALL_PLUGIN
> > definition from conditional?
> It isn't, but it wasn't the point of the constant. The point was to provide
> a safeguard for uninstall.php, not to allow the same callback to be used
> for
> both an uninstall routine and something else.
> You're welcome to open a ticket for it for > 3.0.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

Davit Barbakadze

More information about the wp-hackers mailing list