Aviblock.com

Very often I’ve had to have external scripts access the ExpressionEngine environment, including the database, the sessions, and whatever else. For example, a cron job, or just simple one off scripts. So there are two ways most people do this, both are annoying. The simplest, is to create a template with PHP enabled. This is annoying because of all the extra steps involved, plus you get the overhead of extra database queries. The second is to create a module action. This is even more annoying, less database overhead, but you have to go through extra loops of creating a module and installing it. Plus you get to work with meaningless URL like http://mysite.com?ACT=324.

For EE1, I had distilled out all the code necessary to instantiate all the global EE objects. This was a one time annoyance, and I had to, unfortunately, duplicate a lot (read:all) the code, but it has come in handy many times.

Recently, I had to do this for EE2 as well, and it was not so straightforward.

Of course I began by distilling index.php and CodeIgniter.php, duplicating all that code. The only tricky parts, are that you need a fake “controller”.

I handled this by creating a small class, instantiating it:

class A extends Controller {}
$EE = new A;

Once I got to that point, all I had to do was call:

$EE->core->_initialize_core();

Now you can integrate EE anywhere, including any other systems or frameworks:

$system_path = '/path/to/system';
include 'boostrap-ee2.php';

And we have our $EE super global god object.

The full code is hosted on Github: