[BUG] Fatal error happened when saving related records

[AlloVince]

Hi guys

I would like to save related records for two tables: Tags and Texts, text is belongs to tags by one to one relation. here is test code:

$di = new \Phalcon\DI\FactoryDefault();
$di->set('db', function(){
    return new \Phalcon\Db\Adapter\Pdo\Mysql(array(
        "host" => "localhost",
        "username" => "root",
        "password" => "",
        "dbname" => "scrapy"
    ));
});


class Tag extends Phalcon\Mvc\Model
{
    /**
    *
    * @var integer
    */
    public $id;

    /**
    *
     * @var string
     */
     public $tagName;


    public function getSource()
    {
        return "eva_blog_tags";
    }

    public function initialize()
    {
        $this->hasOne('id', 'Texts', 'post_id', array(
            'alias' => 'Text'
        ));
    }

}

class Text extends Phalcon\Mvc\Model
{
    /**
    *
    * @var integer
    */
    public $post_id;

    /**
    *
     * @var string
     */
     public $content;


    public function getSource()
    {
        return "eva_blog_texts";
    }

}

$tag = new Tag();
$text = new Text();
$tag->Text = $text;

$_POST = array(
    'tagName' => 'foo',
    'Text' => array(
        'content' => 'bar'
    ),
);
/*
//should add below:
$text->assign($_POST['Text']);
unset($_POST['Text']);
*/

$tag->assign($_POST);
$tag->save();

By above code, phalcon will caused a Fatal error:

Fatal error: Phalcon\Mvc\Model::_postSaveRelatedRecords(): Call to method writeattribute() on a non object in /opt/htdocs/phalcon_bugs/model_save_by_sub_array/test.php on line 85

Please notice that I commented few lines, if uncomment these line the demo will be correct. However, I think if input data not correct, phalcon should throw an exception but not caused a Fatal error.

Best regards

[dreamsxin]

The data Text is overwrite model's Relation Text.

$_POST = array(
    'tagName' => 'foo',
    'Text' => array(
        'content' => 'bar'
    ),
);

I fix it.

[dreamsxin]

Can you test it again?

[AlloVince]

As my test this issue have been fixed, I hope v1.3.2 could release soon. Thank you.