9.x.creator, editor, and destroyer all now return a BelongsTo relation.Full Changelog: https://github.com/mattiverse/Laravel-Userstamps/compare/3.1.1...4.0.0
Full Changelog: https://github.com/mattiverse/Laravel-Userstamps/compare/3.1.0...3.1.1
This release introduces macros to simplify creating migrations.
Userstamp columns can now be created with:
$table->userstamps();
$table->userstampSoftDeletes();
And dropped with:
$table->dropUserstamps();
$table->dropUserstampSoftDeletes();
Full Changelog: https://github.com/mattiverse/Laravel-Userstamps/compare/3.0.0...3.1.0
8.2 and Laravel versions lower than 9.x.Wildside\Userstamps to Mattiverse\Userstamps to reflect the ownership change of this project.Userstamps trait has moved from Wildside\Userstamps\Userstamps to Mattiverse\Userstamps\Traits\Userstamps - note the additional nesting under Traits.Full Changelog: https://github.com/mattiverse/Laravel-Userstamps/compare/2.5.0...3.0.0
Full Changelog: https://github.com/mattiverse/Laravel-Userstamps/compare/2.4.0...2.5.0
Adds support for Laravel 11.x
Adds support for Laravel 10.x
Adds support for Laravel 9.x
Adds support for Laravel 8.x.
This releases contains no new functionality, but has a breaking change for an undocumented behaviour.
The majority of use cases should not be effected by this change, but tagging a major version in case anyone was relying on the behaviour.
Previously, setting any of CREATED_BY, UPDATED_BY and DELETED_BY class constants to null would revert to the default column name. This release changes that behaviour to match Laravel's pattern for the timestamp class constants. A value of null on any of those class constants will now disable maintaining of that column.
Adds support for Laravel 7.x.
Remove use of helper method unsupported by Lumen.
New helper methods are available to workaround limitations with Eloquent events when performing bulk updates or deletes.
updateWithUserstamps and deleteWithUserstamps behave exactly the same as update and delete, but allow you to make bulk updates that maintain the correct updated_by and deleted_by values.
New helper methods are available to workaround limitations with Eloquent events when performing bulk updates or deletes.
updateWithUserstamps and deleteWithUserstamps behave exactly the same as update and delete, but allow you to make bulk updates that maintain the correct updated_by and deleted_by values.
Fixes an issues where the creator, editor and destroyer methods would resolve to the incorrect class.
Breaking changes
updated_by could be set to null, overwriting the last set value, if no user is present.Adds support for Laravel 6.x.
Adds support for Laravel 5.8.
Fixes a bug causing unnecessary events from being fired when a model is softly deleted.
Thanks to @mazyvan for the fix.
Adds support for Laravel 5.7.
The creator, editor and destroyer methods now respect custom column names.
Thanks to @tayfunkayahan for their help with this one.
Setting the UPDATED_BY constant to null will now disable maintaining an updated_by column.
Allow custom created_by, updated_by and deleted_by column names.
Support Laravel 5.6
Thanks to @tbirrell and @RomeroMsk for their input on this release.
Don't override created_by or updated_by when creating, if already set.
Don't override deleted_by when deleting, if already set.
Ensures SoftDeletes are correctly detected when loaded by a parent class.
Fixes a bug blocking deleted_by being set when fired on multiple records at once.
Fixes a bug breaking compatibility with Laravel 5.1
New methods allow you to stop and start userstamping on a model.
No behaviour has changed as userstamps will continue to be automatically maintained - you just now have the option to chose otherwise.
Adds new methods for checking who created, updated and deleted models.
When creating a model the updated_by column will now be set to match created_by as per behaviour in Laravel of created_at and updated_at.
Improved method used to detect SoftDeletes trait
Match PHP requirements with Laravel 5.1 LTS
How can I help you explore Laravel packages today?