-
Notifications
You must be signed in to change notification settings - Fork 23
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
NoMethodError when trying to access history #17
Comments
@SuperMasterBlasterLaser can you please give me step to reproduce the issue ? I tried and it's working fine for me. |
I solved this problem by using monkey patch. |
@SuperMasterBlasterLaser what was the solution that you implemented to fix this? I'm having the same problem. |
I forked mongoid-audit and in
|
Thanks @SuperMasterBlasterLaser. Actually -- I just realized that I was getting this error until I ran the migration that is listed in the README. I had database that was set up with the previous version of
Hope this helps someone else coming across this. |
Actually -- after running the migration, I'm still running into this issue intermittently. It seems like restarting the server resolves this, but it keeps coming up at runtime. |
I Have everything done accrodingly to your guide. When I open my history_index page.
It gives me this error:
undefined method `updater' for #HistoryTracker:0x00000012bf62f8
The text was updated successfully, but these errors were encountered: