Description: ------------ While looping through a find() and adding getLinks() to each loop I was hoping to use toArray() to get a multidimensional array. Instead it appears that toArray() does not, in fact, return links. Reproduce code: --------------- $foo = new DataObjects_foo $foo->categoryID = 1 if($foo->find()) { $arr = array(); while($foo->fetch()) { $foo->getLinks(); $arr[] = $foo->toArray(); } } Expected result: ---------------- If my links.ini file had: [foo] categoryID = categories:categoryID You would think I'd get an array that had everything from foo and then [categoryID] => array('categoryID' => 1, 'name' =>'My category') but it doesn't. Actual result: -------------- It just returns the basic dataobject as an array with no link information. Putting a class in there instead via __clone() works as expected.

good point... - I'll have a look at this to see if it's possible.

Fixed In CVS. it should return the link in the array, and also convert those links into arrays. let me know if it works.

This fix isn't working for me. I'm probably doing something wrong, but I now get a 'call to non-object' error (about line 2576 i think) when I call toArray() after getting links. In this loop (from Data_Objects 1.4): foreach($this->_link_loaded as $k) { $ret[sprintf($format,$k)] = $this->$k->toArray(); } $this->$k isn't an object and that's the source of my error. Now, print_r() never has shown a value for _link_loaded on my Data Objects, which probably indicates I am goofing up somewhere, although my links do in fact seem to get loaded. I'm trying to whittle down a case which both a) has links and b) can sucessfully take a toArray() call, to figure out whether this is just a problem with my own code, but I haven't found one yet. On the off chance I'm not doing something wrong, and this is in fact a bug, I guess my suggestion would be to maybe check whether $this->$k is actually an object. I'll try to come up w/ an actual test case, but that's my feedback on what seems like a great addition to toArray() (my code to accomplish this same thing was significantly more convuluted and tied to my own data model)

will check it is cleared corectly..

should be fixed in 1.5.2 hopefully...