-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing columns breaks older logs #70
Labels
Comments
palkan
added a commit
that referenced
this issue
Apr 30, 2018
palkan
added a commit
that referenced
this issue
Apr 30, 2018
palkan
added a commit
that referenced
this issue
Apr 30, 2018
palkan
added a commit
that referenced
this issue
Apr 30, 2018
Fixed by #71 and released as 0.6.4 |
So fast! :D <3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Possibly related to #59
We have this migration:
so,
is_agent
column is now gone, but it is still in the log data.In our admin, we print all changes for a specific record:
Error:
can't write unknown attribute
is_agentAt:
resource.at(version: version)`Stacktrace:
Seems like it could be fixed by the gem. Is there any temporary fix we could do?
UPDATE:
Temporary fix:
resource.log_data.data['h'].map{|l| l['c'].delete('is_agent') }
The text was updated successfully, but these errors were encountered: