Troubleshooting

This is a compilation of common problems and their respective solutions and/or workarounds.

Auditing not working

You followed the documentation to the letter and yet, audit records aren't being created?

This package relies on Eloquent events and if they don't fire, an Audit cannot be created.

The most common mistake is doing an update or delete using a Builder instance, rather than an using an Eloquent Model instance.

Usually, something like this happens:

Article::where('id', $id)->update($data);

When in fact, it should be:

Article::find($id)->update($data);

This error happens when Laravel tries to cache the configuration and you're using a Closure as a User resolver in the config/audits.php file.

Support for Closure and callable resolvers has been removed from version 5.0.0 onwards.

Read the User resolver section in the General Configuration for more information.

False positives cause Audit records to be created. This happens when model attributes are updated with BOOLEAN and/or DATE values.

The internal data of the Eloquent model will be as follows:

In the $attributes array attribute:

In the $original array attribute:

This makes the getDirty() and isDirty() methods to consider wrongful attribute changes when comparing data.

According to a maintainer, this is an expected behaviour.

As a workaround, consider passing 1 and 0, instead of true and false. For date values, append 00:00:00.

At the time of writing, this is the only open issue about this subject.

This might happen in version 4.1.x, because the updated_at column values in the audits table are set to NULL.

After upgrading the table schema for 4.1.x, don't forget to set the updated_at values to match the ones from created_at.

Read the Upgrading documentation for more details.