Question: Why initialize and not startup?

[vincent-fletcher]

I have run into some issues using this plugin with a multi-tenant database structure (isolated databases), because the initialize() function in PrgComponent constructs models before my authentication code has had a chance to figure out which tenant database to use.

I have renamed initialize() function to startup() (so it is executed after my Auth has had a chance to login the user), and everything still seems to be working correctly - but I am wondering whether there is some kind of issue with this beneath the surface that I have not uncovered?

Any info would be much appreciated.

[burzum]

Should be OK to change it to startup(), I'll investigate it a little more and talk to the team before we make a change we might regret in some use case we don't consider right now.

[dereuromark]

I can also not see a reason why it shouldn't work. But looking into it more detailed before doing that sure helps to avoid regressions or future issues. Some use cases might involve other components or the action itself to hook into it which then wouldn't necessarily happen any more in the expected order.

[burzum]

I've made this configurable to preserve backward compatibility. Just configure the component to use startup:

public $components = array(
    'Prg' => array('callback' => 'startup')
);