These are the errors - Exception trace:

PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name ''") C:\wamp64\www\fyp\vendor\laravel\framework\src\Illuminate\Database\Connection.php:457

PDO::prepare("create table `` (id bigint unsigned not null auto_increment primary key, log_name varchar(191) null, description text not null, subject_id bigint unsigned null, subject_type varchar(191) null, causer_id bigint unsigned null, causer_type varchar(191) null, properties text null, created_at timestamp null, updated_at timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci'") C:\wamp64\www\fyp\vendor\laravel\framework\src\Illuminate\Database\Connection.php:457

phpunit --coverage-text --coverage-clover=coverage.clover PHP Fatal error: Declaration of Orchestra\Testbench\TestCase::setUp() must be compatible with PHPUnit\Framework\TestCase::setUp(): void in /home/travis/build/spatie/laravel-activitylog/vendor/orchestra/testbench-core/src/TestCase.php on line 15

I ran the command "composer update" and "laravel-activitylog" updated to version 1.6.0 The event recording the record deletion log was not executed, the record was deleted from the Model table, but was not included in the "activity_log" table.

I'm extending Permission and Role models for laravel-permissions package.

Activity log works as expected when a new Role is created, updated or deleted. Now I'm just wondering how to log any activity related to model_has_roles and role_has_permissions tables to keep track when roles are assigned to a user or permissions are attached to roles.

Having a CRUD for system users where roles can be attached/detached adds/removes records from model_has_roles table, but no activity is being logged.

Do I need to extend pivot tables or implement anything else in my custom Models? This is how my custom Role model looks like:

<?php

namespace App;

use Spatie\Permission\Models\Role as Roles;

// Activity Log
use Spatie\Activitylog\Traits\LogsActivity;
use Spatie\Activitylog\Contracts\Activity;

class Role extends Roles
{
    //
    use LogsActivity;

    protected $table    = 'roles';
    protected $fillable = ['name','title','guard_name'];

    // Activity Log
    protected static $logFillable = true;
    protected static $submitEmptyLogs = false;
    protected static $logOnlyDirty = true;
}

Any help will be appreciated. Thanks in advance

Edit: BTW, my controllers are using custom models such use App\Role; Edit 2: Roles are assigned to Users using $user->roles()->sync($roles);

When using a package like spatie's own schemaless-attributes, the extra attributes are logged as being different every touch of the model, which not only generates useless logs even when using $logOnlyDirty but just creates confusion in the activity log itself. While specifying specific json attributes is supported, that functionality isn't carried over into the dirty checks to confirm that what's going into the activity log is only specifically changed json attributes. Additionally, the reverse filtering that normally works isn't applied either (being able to set logAttributes = *, and then exclude attributes from ever being logged).

It seems that there was quite a bit more that needed to be done to add json attribute logging that what's currently there. On top of that, in enabling that functionality or really handling any deep diffing is completely unsupported.

I was interested to use this package with mongodb and the jenssegers/laravel-mongodb. To make it easier to use packages like jenssegers/laravel-mongodb, I have removed the obligation to extend your model Activity. I created an Activity interface and I modified the control in the ServiceProvider so that Activity model should implement the Activity interface and extend Illuminate\Database\Eloquent\Model. In this way, to use this package with MongoDB it is sufficient to create an activity class like the following one

use Spatie\Activitylog\Contracts\Activity as ActivityContract;
use Illuminate\Support\Collection;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\Relations\MorphTo;
use Jenssegers\Mongodb\Eloquent\Model as Moloquent;
class Activity extends Moloquent implements ActivityContract
{
    protected $table = 'activity_log';
    protected $connection = 'mongodb'; //mongodb connection
    protected $collection = 'activity_log';

I've also modified some test to verify the implementation of the Interface and the extension of Illuminate\Database\Eloquent\Model.

I hope this could be useful for the ones who wants to use this package with mongodb instead of the other database drivers shipped with Laravel.

Thank you.

Best regards, Leonardo Padovani

I M trying to migrate activity log table but it returning error as mention below

SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that cor responds to your MariaDB server version for the right syntax to use near 'json n ull, created_at timestamp null, updated_at timestamp null) default cha' at l ine 1 (SQL: create table activity_log (id bigint unsigned not null auto_incr ement primary key, log_name varchar(191) null, description text not null, s ubject_id bigint unsigned null, subject_type varchar(191) null, causer_id b igint unsigned null, causer_type varchar(191) null, properties json null, c reated_at timestamp null, updated_at timestamp null) default character set ut f8mb4 collate 'utf8mb4_unicode_ci')

config/auth.php

<?php

return [

    'defaults' => [
        'guard' => 'web',
        'passwords' => 'users',
    ],

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],

        'api' => [
            'driver' => 'token',
            'provider' => 'users',
        ],
    ],

    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => APP\User::class,
        ],
    ],

    'passwords' => [
        'users' => [
            'provider' => 'users',
            'email' => 'auth.emails.password',
            'table' => 'password_resets',
            'expire' => 60,
        ],
    ],

];

config/activitylog.php

<?php

return [
    'enabled' => env('ACTIVITY_LOGGER_ENABLED', true),
    'delete_records_older_than_days' => 365,
    'default_log_name' => 'default',
    'default_auth_driver' => null,
    'subject_returns_soft_deleted_models' => false,
    'activity_model' => \Spatie\Activitylog\Models\Activity::class,
    'table_name' => 'activity_log',
];

Database:

I am using Cartalyst/Sentinel for auth, with a modified version of the original Sentinel model. It seems like this package does not know how to get the user, how can I fix this?

Describe the bug for example i have a from & to date columns with values of |from|to| |-----|---| |2021-02-23 00:00:00|2021-02-27 00:00:00|

but when logged they become |from|to| |-----|---| |2021-02-22T22:00:00.000000Z | 2021-02-27T22:00:00.000000Z|

note the -2 hrs diff.

To Reproduce

• set config.app.timezone to something else ex.EET
• create a record
• check the saved log

Expected behavior data should be logged as it is without any changes.

Versions (please complete the following information)

• PHP: PHP 8.0.2 (cli)
• Database: 8.0.23
• Laravel: 8.28.1
• Package: 3.16.1

Hello together,

I would like to log the activities for the permissions. For this I created new Models of roles and permission. But I don't see any log in the database:

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;
use Spatie\Permission\Models\Permission as SpatiePermission;
use Spatie\Activitylog\Traits\LogsActivity;
use Illuminate\Database\Eloquent\SoftDeletes;

class Permission extends SpatiePermission
{
    use LogsActivity;
	/** The following change of attributes will be logged. */
	//protected static $logAttributes = ['name', 'text'];
	
	/** Alternativly we can define that following attribute changes should be not recoreded */
	//protected static $ignoreChangedAttributes = ['text'];
	
	/** Only the `deleted` event will get logged automatically */
    //protected static $recordEvents = ['deleted'];
	protected static $logOnlyDirty = true;

	//use SoftDeletes; // ad in schema $table->softDeletes();
}

config/permissions.php

<?php

return [

    'models' => [

        /*
         * When using the "HasRoles" trait from this package, we need to know which
         * Eloquent model should be used to retrieve your permissions. Of course, it
         * is often just the "Permission" model but you may use whatever you like.
         *
         * The model you want to use as a Permission model needs to implement the
         * `Spatie\Permission\Contracts\Permission` contract.
         */

        // 'permission' => Spatie\Permission\Models\Permission::class,
		'permission' => \App\Models\Permission::class,

        /*
         * When using the "HasRoles" trait from this package, we need to know which
         * Eloquent model should be used to retrieve your roles. Of course, it
         * is often just the "Role" model but you may use whatever you like.
         *
         * The model you want to use as a Role model needs to implement the
         * `Spatie\Permission\Contracts\Role` contract.
         */

        //'role' => Spatie\Permission\Models\Role::class,
		'role' => \App\Models\Role::class,

    ],

Did I missed anything?

Thank you.

Really nice package! Is there a way to log only dirty fields? Currently I have to do a small hack like so:

protected static $logAttributes = [];     

public static function boot()
{
    parent::boot();
    static::saving(function (Model $model) {
        static::$logAttributes = array_keys($model->getDirty());
    });
}

Would be nice to have something baked in.

Describe the bug I have a to deploy my project into cpanel. But when i deploy it, there is an error to load activity log in the browser.

To Reproduce

Expected behavior It should load the activity log in browser

Screenshots

Versions (please complete the following information)

• PHP: 8.1
• Database: MySQL (PhpMyAdmin)
• Laravel: 8.75
• Package: 4.6

Exception Symfony\Component\ErrorHandler\Error
FatalError

Could not check compatibility between Spatie\Activitylog\Models\Activity::getExtraProperty(string $propertyName, ?Spatie\Activitylog\Models\mixed $defaultValue = NULL): Spatie\Activitylog\Models\mixed and Spatie\Activitylog\Contracts\Activity::getExtraProperty(string $propertyName, Spatie\Activitylog\Contracts\mixed $defaultValue): Spatie\Activitylog\Contracts\mixed, because class Spatie\Activitylog\Models\mixed is not available

Stack Trace Could not check compatibility between Spatie\Activitylog\Models\Activity::getExtraProperty(string $propertyName, ?Spatie\Activitylog\Models\mixed $defaultValue = NULL): Spatie\Activitylog\Models\mixed and Spatie\Activitylog\Contracts\Activity::getExtraProperty(string $propertyName, Spatie\Activitylog\Contracts\mixed $defaultValue): Spatie\Activitylog\Contracts\mixed, because class Spatie\Activitylog\Models\mixed is not available

in /home/lppmitenasac/simpenmas2.itenas.ac.id/vendor/spatie/laravel-activitylog/src/Models/Activity.php(line 74)

Bumps actions/stale from 6.0.1 to 7.0.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Describe the bug I ran into a problem earlier today so basically the index PRIMARY for table activity_log is corrupted. I do have almost 20k rows in the table. I tried to do OPTIMIZE TABLE but that was not successful.

To Reproduce I don't actually know how to re-produce that. I have an application up and running for almost 3 years and the table has 20k rows.

Expected behavior The index should NOT be corrupted.

Screenshots

Versions (please complete the following information)

• PHP: 7.2.17
• Database: MariaDB 10.0.38
• Laravel: 5.8.7
• Package: 3.2

Describe the bug SQLSTATE[01000]: Warning: 1265 Data truncated for column 'subject_id' at row 1,

To Reproduce Things needed to reproduce the error. seed

$project = Project::create([
            'title' => 'Project 1',
            'description' => 'Project 1 description',
            'budget' => 10,
            'release_date' => now()->addDays(10),
            'status' => ProjectStatusEnum::pending->value,
            'payment_status' => ProjectPaymentStatusEnum::pending->value,
            'freelancer_id' => 1,
            'customer_id' => 2,
        ]);

        $project->targets()->create([
            'title' => 'Target 1',
            'details' => 'Target 1 details',
            'user_id' => 2,
            'duedate' => now()->addDays(5),
            'budget' => 5,
            'status' => ProjectTargetStatusEnum::pending->value,
            'payment_status' => ProjectTargetPaymentStatusEnum::pending->value,
        ]);

        $project->targets()->create([
            'title' => 'Target 2',
            'details' => 'Target 2 details',
            'user_id' => 2,
            'duedate' => now()->addDays(9),
            'budget' => 5,
            'status' => ProjectTargetStatusEnum::pending->value,
            'payment_status' => ProjectTargetPaymentStatusEnum::pending->value,
        ]);

Model: normal

Expected behavior seed this data

Screenshots

Versions (please complete the following information)

• PHP: 8.1.2
• Database: 10.4.22-MariaDB
• Laravel: 9.38.0
• Package: 4.7.2

Additional context I need to seed this data and i Log Activity in Project and ProjectTarget model

Exception

  Illuminate\Database\QueryException 

  SQLSTATE[01000]: Warning: 1265 Data truncated for column 'subject_id'

Stack Trace

\vendor\laravel\framework\src\Illuminate\Database\Connection.php:760
    756▕         // If an exception occurs when attempting to run a query, we'll format the error
    757▕         // message to include the bindings with SQL, which will make this exception a
    758▕         // lot more helpful to the developer instead of just the database's errors.
    759▕         catch (Exception $e) {
  ➜ 760▕             throw new QueryException(
    761▕                 $query, $this->prepareBindings($bindings), $e
    763▕         }
    764▕     }

Bumps stefanzweifel/git-auto-commit-action from 4.15.4 to 4.16.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.