Scott Dawson

Ardent should ignore create. Are you saying you want Ardent to perform validation on create as well as save?

[Create already actions save](http://laravel.com/api/source-class-Illuminate.Database.Eloquent.Model.html#334-347) so you don't need to. I assume the validation error is that the title already exists? If you must use the code you have, use update...

Further to this, if I remove the validation rules from the model the error also goes away so it's localised to testing + validation rules. I'm using these rules for...

I created a fork/clone of Arent which does just that: https://github.com/lakedawson/vocal

Ardent passes validation off the Laravel's validator class. You can set custom validation messages in the same way you would directly using the validator class.

Do you have [`autoPurgeRedundantAttributes` set to true](https://github.com/laravelbook/ardent#purge)? This should remove `_token` and `_method`. Alternatively for [mass assignment](http://laravel.com/docs/eloquent#mass-assignment) you can also use `fillable`: ``` php protected $fillable = array('username', 'password', 'email');...

This can be done by editing the ardent save method, and if `$record->exists == 1` build unique exclusion rules. Like this: https://github.com/sjdaws/ardent/commit/d007d1846ae11d78549d2213f2d440e7e57d1ad0 If you want to do the same thing...

This is a Laravel issue not an Ardent issue. The `unique` rule works exactly the same way as a database unique would work, the value can only appear once in...

Fillable will assign anything which is passed. Because models aren't aware of the underlying database you can't set a field to null if it's not defined. Your best bet would...