Whenever a plugin creates a new MyClass();
, it should assign it to a uniquely named variable. That way, the instance of the class is accessible.
So if he was doing $myclass = new MyClass();
, then you could do this:
global $myclass;
remove_action( 'wp_footer', array( $myclass, 'my_action' ) );
This works because plugins are included in the global namespace, so implicit variable declarations in the main body of a plugin are global variables.
If the plugin doesn't save the identifier of the new class somewhere, then technically, that's a bug. One of the general principles of Object Oriented Programming is that objects which are not being referenced by some variable somewhere are subject to cleanup or elimination.
Now, PHP in particular doesn't do this like Java would, because PHP is sorta a half-arsed OOP implementation. The instance variables are just strings with unique object names in them, sort of thing. They only work because of the way the variable function name interaction works with the ->
operator. So just doing new class()
can indeed work perfectly, just stupidly. :)
So, bottom line, never do new class();
. Do $var = new class();
and make that $var accessible in some way for other bits to reference it.
Edit: years later
One thing I've seen a lot of plugins doing is to use something similar to the "Singleton" pattern. They create a getInstance() method to get the single instance of the class. This is probably the best solution I've seen. Example plugin:
class ExamplePlugin
{
protected static $instance = NULL;
public static function getInstance() {
NULL === self::$instance and self::$instance = new self;
return self::$instance;
}
}
The first time getInstance() is called, it instantiates the class and saves its pointer. You can use that to hook in actions.
One problem with this is that you can't use getInstance() inside the constructor if you use such a thing. This is because the new calls the constructor before setting the $instance, so calling getInstance() from the constructor leads to an infinite loop and breaks everything.
One workaround is to not use the constructor (or, at least, not to use getInstance() within it), but to explicitly have an "init" function in the class to set up your actions and such. Like this:
public static function init() {
add_action( 'wp_footer', array( ExamplePlugin::getInstance(), 'my_action' ) );
}
With something like this, at the end of the file, after the class has been all defined and such, instantiating the plugin becomes as simple as this:
ExamplePlugin::init();
Init starts to add your actions, and in so doing it calls getInstance(), which instantiates the class and makes sure only one of them exists. If you don't have an init function, you would do this to instantiate the class initially instead:
ExamplePlugin::getInstance();
To address the original question, removing that action hook from the outside (aka, in another plugin) can then be done like so:
remove_action( 'wp_footer', array( ExamplePlugin::getInstance(), 'my_action' ) );
Put that in something hooked to the plugins_loaded
action hook and it'll undo the action being hooked by the original plugin.