[eluser]WanWizard[/eluser]
It bugged me, so I went looking, and I think I found it.
The method _to_object() is responsible for creating objects out of query results. It requires the DMZ object and a row object as parameters. This works ok on the main query.
When it is done creating a DMZ object, it checks if there are instantiations of other objects that needs to be created (which is the case if you use an include_related with $instantiate = TRUE). It does that by creating an empty object for the related model (by calling _get_without_populating), and then copying the row retrieved in the related query to the new object by calling _to_object() again, this time with the related object and the retrieved row for that object.
This is the moment where it goes wrong. The row passed here is created just before that call, as an array, not as an object. Therefore, when _to_object is called, the "if (! isset($row->{$field}) " test fails, causing all object fields to be reset to NULL.
If you change the call so that the row is passed as an object, instantiation works properly:
Code:
// set the values, make sure $row is passed as an object
$c->_to_object($c, (object) $row);
