You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Paper trail 14 seems to break in ways I was not expecting in environments without users. Given a model
class Something
has_paper_trail
end
Doing something simple like Something.destroy in console results in a User must exist error. This means any changes to the Something model in console or Sidekiq fail even though Something.valid?. For destroy this will cause the original Something to be destroyed but none of its dependent relationships :( A far better way would be to set user to 0 or nil rather than just dying.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
Bug reports must provide a script that reproduces the bug, using our template. Feature suggestions must include a promise to build the feature yourself.
Thank you for all your contributions.
Paper trail 14 seems to break in ways I was not expecting in environments without users. Given a model
class Something
has_paper_trail
end
Doing something simple like Something.destroy in console results in a User must exist error. This means any changes to the Something model in console or Sidekiq fail even though Something.valid?. For destroy this will cause the original Something to be destroyed but none of its dependent relationships :( A far better way would be to set user to 0 or nil rather than just dying.
The text was updated successfully, but these errors were encountered: