Summary of problem or feature request

Add Laravel 7.0 support

Code snippet of problem

System details

• Operating System
• PHP Version
• Laravel Version
• Laravel-Auditable Version

Summary of problem or feature request

As listed in the subject, whenever using the soft deletes, it fails to update the deleted_by column yet deleted_at is being updated. I don't know if this has always happened or if its a recent occurrence, but checking the tables, it would appear as if it has always been this way.

Code snippet of problem

Migration:

Schema::create('incidents', function (Blueprint $table) {
    $table->increments('id');
    $table->auditableWithDeletes();
    $table->timestamps();
    $table->softDeletes()
});

Model

namespace App;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\SoftDeletes;
use Yajra\Auditable\AuditableWithDeletesTrait;

class Incident extends Model
{
    use AuditableWithDeletesTrait, SoftDeletes;
}

IncidentController

Incident::where($request->input('incident_id'))->delete();

System details

• Operating System - CentoOS in Docker
• PHP Version - 7.3.2
• Laravel Version - 7.x
• Laravel-Auditable Version - Current stable

Summary of problem or feature request

Setting the updated_by field in a Factory has no effect as the value is overwritten by null on save due to there being no currently authenticated user.

Code snippet of problem

    public function definition()
    {
        return [
            'name' => $this->faker->name,
            'email' => $this->faker->unique()->safeEmail,
            'email_verified_at' => now(),
            'password' => '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', // password
            'remember_token' => Str::random(10),
            'created_by' => 3, // Stamped as 3
            'updated_by' => 3, // Stamped as NULL
        ];
    }

System details

• Operating System - PopOS
• PHP Version - 7.4.9
• Laravel Version - 8.21.0
• Laravel-Auditable Version - 4.3.0

To detect model use "soft delete"

in src/AuditableTraitObserver.php:

if ($model->getConnection()->getSchemaBuilder()->hasColumn($model->getTable(), $deletedBy)) {

It would be better to use (faster without calling the db)

if (method_exists($model, 'getDeletedAtColumn')) {

That method will exist if the "soft delete" trait was used

https://laravel.com/api/5.8/Illuminate/Database/Eloquent/SoftDeletes.html#method_getDeletedAtColumn

Hello,

will there be an update for Laravel 9 Support?

Hi,

Will this still work with Laravel 5.8?

Thanks

Laravel 7

Actual Behaviour
Do not save log when a use DataTables MassDestroy, if i remove just only one, log save OK.

Model friends.php

namespace App;

use App\Traits\Auditable;
use Yajra\Auditable\AuditableWithDeletesTrait;`

class ProcedureType extends Model
{
    use SoftDeletes, MultiTenantModelTrait, Auditable, AuditableWithDeletesTrait;

   protected $dates = [
        'created_at',
        'updated_at',
        'deleted_at',
    ];
 protected $fillable = [
        'title',
        'created_at',
        'updated_at',
        'deleted_at',
        'created_by_id',
    ];

Controller app\http\admin\FriendsController.php

public function destroy(Friends $friends)
    {
        abort_if(Gate::denies('friends_delete'), Response::HTTP_FORBIDDEN, '403 Forbidden');

        $friends->delete();

        return back();

    }
public function massDestroy(MassDestroyFriendsRequest $request)
    {
        Friends::whereIn('id', request('ids'))->delete();

        return response(null, Response::HTTP_NO_CONTENT);

    }

Steps to Reproduce
composer require yajra/laravel-auditable

composer update

open my friends page

select 2 or more on checkbox and click em Mass Destroy (datatables)