register_activation_hook(__FILE__ , ‘old_function’);
function old_function() {
add_action(‘plugins_loaded’ , ‘new_activation_function’);
}

function new_activation_function() {
echo “etcetera”;
add_option(‘__new_activation_function’, ‘bla’);
die;
}

If I’m hearing you correctly to this point – and I think I am – the only place this wouldn’t work for you with WP 2.8 is on the register_activation_hook(). Why not take whatever the guts of your activation hook are and postpone them a couple of seconds.

ie:
register_activation_hook( __FILE__ , ‘old_function’);
function old_function(){
add_action(‘plugins_loaded’ , ‘new_activation_function’);
}

In that scenario, new_activation_function() would only be called if the plugin was being activated (that’s the point, right) and, it would be called, after all the other plugins’ functions are available.

I understand the argument “We need a patch” and agree, but I believe this would work in the mean time.

If you know of a hook that fires before register_activation_hook(), but after all plugins are loaded, please let me know.

First, switch the “dependent” and “required” plugin variables. Second, put the script in Akismet instead of Hello Dolly and you can’t activate Akismet unless Hello Dolly is activated.

If “Hello Dolly” was instead named “AA Hello Dolly”, it would be loaded before Akismet and not work.

So, about the other problem:

I added a function to Hello Dolly and then I went over to Akismet and tried to call it.

I understand that its going to die if its referenced before its defined. My question is… in what scenario would that need to happen? Meaning, whatever you're trying to do when Akismet loads, why can't place it in an action and call it just a little bit later?