-
Notifications
You must be signed in to change notification settings - Fork 513
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 callbacks stopped working after upgrading to 1.2.0 #289
Comments
did some further analysis and it turns out that the issue occurs only when invoking the event using a web request and update_attributes. |
Did you find any solution for this? We are having a similar problem here with the following transition: state_machine :state, initial: :draft do
event :process do
transition [:draft, :crashed] => :processing
end
after_transition any => :processing do |activity, transition|
# This is never called
end
end I have re-created the very same state machine in an empty class, and there it works. So it has to be some side-effect by something else in the class, but it's a quite complex one and I couldn't find the answer yet. |
In our case, the rollback to statemachine v1.2.0 didn't solve the problem though, it seems to be the upgrade from Rails3.2 to Rails4. |
Maybe this is related? #280 |
Hi,
My after callbacks are no longer executed after upgrading from 1.1.2 to 1.2.0.
I confirmed that by rolling back to 1.1.2:
Following is the state machine with the after callback any => :active
The text was updated successfully, but these errors were encountered: