Record the change log from models in Laravel

Is it correct that any updated relations are not being logged in the database? I'm using eloquent's sync() function a lot, for updating many-to-many relations...

Any ideas how to do that?

| Q | A | ----------------- | --- | Bug? | no | New Feature? | yes | Framework | Laravel | Framework version | 6.0 | Package version | 9.2.0 | PHP version | 7.3

Actual Behaviour

I can't upgrade to Laravel 6.0 because owen-it/laravel-auditing v9.2.0 requires illuminate/filesystem ^5.8

Expected Behaviour

Upgrading to 6.0

Steps to Reproduce

• Update laravel/framework to 6.0
• composer update

@devthiagolino Os meus logs aparecem assim:

user.name atualizou os dados de SANTA CATARINA1 De: old.uf -> Para: new.uf updated in 2015-10-02 02:33:45 De: SANTA CATARINA -> Para: SANTA CATARINA1 updated in 2015-10-02 02:33:45 user.name atualizou os dados de SANTA CATARINA De: old.uf -> Para: new.uf updated in 2015-10-02 11:01:41 De: SANTA CATARINA1 -> Para: SANTA CATARINA updated in 2015-10-02 11:01:41

2 duvidas por mais obvias pois estou comecando a utilizar o laravel:

1. Por que ao inves do nome do usuario aparece user.name ? Tenho que fazer um relacionamento das tabelas logs e users ?
2. Como suprimir os logs onde old.campo e new.campo são nulos ?

A aplicação funciona perfeitamente em ambiente de desenvolvimento, subo para o servidor de produção, rodo a migrate e nada! Trait 'OwenIt\Auditing\AuditingTrait' not found

• isnt it possible to just use the package by simply including the trait ? why do i have to implements AuditableContract for every model ?

• for user model

'user' => [
        'primary_key' => 'id',
        'foreign_key' => 'user_id',
        'model'       => App\User::class,
        'resolver'    => App\User::class,
    ],

it should be enough setting a model value and then the package gets it and do its ops internally, this now removes the steps of having to implements UserResolver & manually adding

public static function resolveId()
    {
        return auth()->check() ? auth()->user()->getAuthIdentifier() : null;
    }

This is being submitted as a preliminary request for comments. It is currently functional, both with local and remote disks, but I'm open to suggestions for improvements.

| Q | A | ----------------- | --- | Bug? | yes | New Feature? | no | Framework | Laravel | Framework version | 5.4.25 | Package version | 4.0.7 | PHP version | 7.0.18

Actual Behaviour

It is not possible to get a Model Audit's User if the User Model uses a non-default Primary Key (ie. a Primary Key different than id).

Expected Behaviour

It should be possible :-)

Steps to Reproduce

• Setup Laravel and Auditing.
• Change the App\User model's Primary Key to something else (like some_id) both in the Model (via the protected $primaryKey property) and the database.
• Add an auditable model:

<?php

namespace App;

use Illuminate\Database\Eloquent\Model;
use OwenIt\Auditing\Auditable;
use OwenIt\Auditing\Contracts\Auditable as AuditableContract;

class SomeModel extends Model implements AuditableContract
{
    use Auditable;

    public $timestamps = false;

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = [
        'field1', 'field2', 'field3',
    ];
}

• Add a table for the new model with a migration with:

Schema::create('some_models', function (Blueprint $table) {
        $table->increments('id');
        $table->string('field1');
        $table->string('field2');
        $table->string('field3');
    });

• Run a simple test like:

public function testAudits()
{
    $modelFields = [
        'field1' => 'Field '.rand(),
        'field2' => 'mail'.rand().'@mail.com',
        'field3' => 'password'.rand(),
    ];

    $model = new SomeModel($modelFields);

    // set a proper ID in here
    Auth::onceUsingId(1);
    $model->save();

    // get model with audits and users
    $model = SomeModel::with('audits.user')->find($model->getKey());

    echo "model: \n";
    print_r($model->attributesToArray());

    $audit = $model->audits->first();

    echo "audit: \n";
    print_r($audit->attributesToArray());

    $user = $audit->user;

    echo "user: \n";
    print_r($user->attributesToArray());
}

Result:

1) Tests\Unit\SomeModelTest::testAudits
Error: Call to a member function attributesToArray() on null

(on the print_r($user->attributesToArray()); line)

Possible Solutions

I got it working by adding a 'user_id' parameter to the Audit::model() method so it looks like:

public function user()
{
    return $this->belongsTo(Config::get('audit.user.model'), 'user_id');
}

Changes

• Added config option for morphable mode. Everything defaults to 'single mode', to maintain backwards compatibility.
• Added config option for guard order.
• Changed current UserSolver to UserIdSolver.
• Added UserIdSolver and UserClassSolver.
• Added commented value to migration file, which needs to be uncommented for morphable to work.
• Added tests to include new classes.
• Adjusted tests to test both modes.

| Q | A | ----------------- | --- | Bug? | no | New Feature? | probably | Framework | Laravel | Framework version | 5.5.17 | Package version | 4.1.3 | PHP version | 7.1.4

Question

Is there a halfway elegant way for programmatically restoring an old state (i.e. using e.g. the third Audit of a model and applying its diff to the model), like either a Laravel framework or an Auditing function?

I'm looking to do something like:

$user->rollback($user->audits->first());

or

$user->rollback(Carbon::createFromDate($year, $month, $day));

If not, would the maintainers consider this a core function of this package or should it be put into an external library?

| Q | A | ----------------- | --- | Bug? |yes | New Feature? | no | Framework | Laravel|Lumen | Framework version | 5.6 | Package version | 8.0 | PHP version | 7.2.8

Actual Behaviour

I want to audit if i delete the model with composite key in Model:
protected $primaryKey = ['roleID', 'menuPermissionID']; public $incrementing = false;

using model: $result = $this->model->where('roleID',$roleId)-> where('menuPermissionID',$menuPermissionID)>firstOrFail(); $result->delete();

Expected Behaviour

it should delete and save to audit trail. right now there is an error during delete. however if i used this query $this->model->where('roleID',$roleId)->delete(); it will delete but it won't audit trail. current error: array_key_exists(): The first argument should be either a string or an integer

Hi, Im using Laravel 5.2 and Auditing 3.1.
When updating a post, only the USERS table writes the UPDATED action. The other tables do not. Below are sample images:

My USER model - UPDATED works fine

My NEWS Model - UPDATED do not record in audits table:

| Bug? | no|yes | New Feature? | no|yes | Framework | Laravel | Framework version | 8 | Package version | 13 | PHP version | 8

Actual Behaviour

hi, i need some help, i'm trying to make a custom Audit model to add the sofdeleted models, but it doesn't work may i made any mistakes. first i copied the Audit.php model of the package and then i did the implementation on my app\config.php, but anyway it doesn't work. i read the doc for the softdelete but for me isn't so clear and i can't make it work :( the only solution to my problem at this moment is adding ->withTrashed() to functions in trait in the vendor folder, but i'd like to avoid that.

Expected Behaviour

i've read that the functions would be added to the model and not to the trait, but in my package (v.13) is still in the trait

Possible Solutions

make the documentation for implementing the softdelete easier

if anyone can help, thanks

Hi guys, can somebody help me with this issue? If I give the transitionTo function an audit before let's say 3 versions, then it only applies the changes from version 3 and not also from 0,1 and 2. That would be annoying if you had to manually apply all the "between"-changes. Or did I missed something here? I assumed that the package does this automatically? If I want to revert to a specific version, with all changes made till then, do I need to iterate through all the audits and apply the changes manually?

It's not a bug

Is it possible to make a manual audit?. I have a lot of funcitons on my model observer, and i need to audit when i execute update in quietly mode. Is it possible?

Thanks

I have installed Laravel Auditing package, now when i insert or update data in Unicode format it store in database like: {"name":"\u0627\u062d\u0645\u062f\u0627\u0644\u0644\u0647","email":"[email protected]","branch_id":"1","id":20}

When enabling strict mode: https://laravel.com/docs/9.x/eloquent#configuring-eloquent-strictness

Model::shouldBeStrict(! $this->app->isProduction());

It will print an error:

The attribute [auditEvents] either does not exist or was not retrieved for model [App\Models\User].