DataMapper ORM v1.8.2

[eluser]Mark Price[/eluser]
[quote author="WanWizard" date="1344589781"]Thanks for the feedback. I've never used MX, but I try to support it as many people do.

I find this a bit of an odd fix.

The purpose of this line is to see if MX_Lang is loaded. The "false" just makes sure the DM autoloader isn't triggered. CI itself doesn't have an autoloader, so either MX is loaded before Datamapper, and then this line works, or MX is loaded after Datamapper, which will never work.

My guess is that you haven't loaded MX before you load Datamapper, and that removing the parameter will activate the DM autoloader, which will now load the MX_Lang library for you (as it only filters CI and EE libraries).

So the proper solution is: make sure you have MX active before you load Datamapper.[/quote]

I did some more digging on this and discovered that MX loads the MX_Lang class with the CI_Loader. Unfortunately, CI_Lang and DM_Lang get loaded right before this.

The fix I came up with for now is to create a MY_Lang class in my core directory that that includes MX_Lang so that it will load when the CI_Lang class loads:

Code:

<?php (defined('BASEPATH')) OR exit('No direct script access allowed');

/* load the MX_Lang class */
require APPPATH."third_party/MX/Lang.php";

class MY_Lang extends MX_Lang {}