Laravel 4.2 soft delete doesn't work with Ardent

[IntellectProductions]

Ok so Laravel 4.1 with the protected $softDelete = true works fine with Ardent. But when you upgrade to Laravel 4.2, it doesn't work anymore since they changed the way soft delete is set. It will still remove the record, but it will remove it permanently instead of updating the deleted_at column.. Do you know when there will be a fix for this?

http://laravel.com/docs/upgrade#upgrade-4.2

Thanks!

[CasperLaiTW]

Hi, I got same problem and I fix.
You can try #212 patch.

[divdax]

Please merge! 😄

[IntellectProductions]

Awesome thank you ! :D

[mspivak]

This is actually not fixing it. Check this one out: #227

[chriskonnertz]

Is there actually someone still maintaining Ardent? Doesn't look like someone is working on a fix or at least a workaround for this problem.

[wizardist]

Is there actually someone still maintaining Ardent? Doesn't look like someone is working on a fix or at least a workaround for this problem.

As you can see, the latest commit was submitted on Jul 10. Could anyone reach the maintainers?

[jloosli]

On a related note, I was able to get the soft delete to work by using

protected $softDeletes = true

in addition to

use SoftDeletingTrait;
protected $dates = ['deleted_at'];

However, calling

$user = User::withTrashed()->where( 'id', $id )->first();
// At this point, I've verified that a user is found
$user->restore();
// Should be restored at this point
$user = User::find($id);
// However $user is null after searching for this $id.

I've also tried

$user->deleted_at = null;
$user->save();

and that doesn't seem to work either.

[divdax]

For me Ardent is dead. It's not really be maintained any more...
Now i'm using https://github.com/dwightwatson/validating

[chriskonnertz]

@jloosli Yep, I also tried the "protected $softDeletes = true" trick but it's not solving all problems...