Skip to content
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

After trigger event #10

Open
pragmaticivan opened this issue Mar 17, 2015 · 4 comments
Open

After trigger event #10

pragmaticivan opened this issue Mar 17, 2015 · 4 comments

Comments

@pragmaticivan
Copy link

I'm getting this warning after trigger an state machine event:

DEPRECATION WARNING: `serialized_attributes` is deprecated without replacement, and will be removed in Rails 5.0.
@rosskevin
Copy link
Member

@pragmaticivan is there a stack trace that leads you to this gem causing it? serialized_attributes doesn't appear to occur in this codebase or that of the parent project. It may be that this is in your codebase and because of callbacks, it looks like it is coming from state_machines?

@catherinetcai
Copy link

@rosskevin - It looks like a change that might have to be made in the gem. Paper Trail had the same issue: paper-trail-gem/paper_trail#416

@rosskevin
Copy link
Member

It looks like this is confirmed to be unrelated to state_machines. Even though state_machines will be somewhere in the call stack, it seems to be other gems or an AR related issue.

Agreed?

@mbulat
Copy link

mbulat commented Jun 14, 2016

@pragmaticivan Might you be using activerecord-import? I got the same warning after upgrading to the state-machines gem, which led me here. But the warning indicated a line where I was using activerecord-import. I upgraded activerecord-import and the warning is gone. activerecord import does use serialized_attributes https://github.com/zdennis/activerecord-import/blob/8ba94f7c05b2259f6447aaf8b01ca5f4b0f5e0a2/lib/activerecord-import/import.rb#L595

Obviously it could be some other gem. It's possible after updating to state_machines, code that was not previously running started to work again which is calling the other library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants