[eluser]Maglok[/eluser]
That is exactly why I am wondering what is up. I actually did take a look in the code and the fact that the overall config
does make it auto_populate and a local (in a datamapper model) config
does not makes me think it must be the definition. I have done this a dozen times though and my other models look exactly the same and do work.
I did do a quick check in the constructor of the account model like so:
Code:
echo $this->auto_populate_has_many;
Which did give me proper response that the value is set at the moment in the code execution. Same thing for the post_model_init. I also came back to the variable later on by writing a small custom function that gives me the value of auto_populate_has_many in the view. So the model is quite aware of the value.
I found the following:
Code:
// Load stored config settings by reference
foreach (DataMapper::$config as $config_key => &$config_value)
{
// Only if they're not already set
if (property_exists($this, $config_key))
{
$this->{$config_key} =& $config_value;
}
}
This does not look like the code you quoted, so I might be at the wrong place (though I did search through the datamapper.php library for your quote). The version I am running here is 1.8.2. Obviously I went to check on the version I use in my sandbox environment. That is 1.8.1-dev (cause it can be unstable I am fine with that).
Did I grab some sort of bad version running 1.8.2?