around_validation error for Rails4.1.0beta

[the-teacher]

Hello!

I have following problem:

Page.last.to_draft
  Page Load (0.2ms)  SELECT "pages".* FROM "pages" ORDER BY "pages"."id" DESC LIMIT 1
   (0.1ms)  begin transaction
   (0.1ms)  rollback transaction
NoMethodError: protected method `around_validation' called for #<StateMachine::Machine:0x00000004382b98>

bin/rails --version
Rails 4.1.0.beta

Maybe it's will be interesting for somebody.

Thank you!

[awsmsrc]

I have this too! Its being caused on a machinist .make! call.
Happy to help with more info!

[awsmsrc]

any update on this?

[awsmsrc]

this is a quick fix, I haven't looked into this more deeply to check for more serious repercussions. With a bit if guidance form a maintainer i'm happy to work on this

[pechorin]

bump, same problem on rails (4.1.0.beta)

[nesrual]

bump - same problem here using Rails 4.1.0.beta

NoMethodError:
  protected method `around_validation' called for #<StateMachine::Machine:0x007fb0c31c5608>

[wkrsz]

PR from @lukeroberts1990 fixes the problem for me (Rails HEAD)

[the-teacher]

Wow wow wow! It's steel doesn't work ((
I can't migrate to rails 4.1.0.beta1

[the-teacher]

config/initializers/state_machine_patch.rb

module StateMachine
  module Integrations
     module ActiveModel
        public :around_validation
     end
  end
end

[sid137]

@the-teacher Thanks! works great

[jurikern]

It's not worked for me, because same error for :around_save protected method (rails 4.1.0.beta1).
Issue (config/initializers/state_machine_patch.rb):

module StateMachine
  module Integrations
     module ActiveModel
        public :around_validation
     end

     module ActiveRecord
        public :around_save
     end
  end
end

[sid137]

@Kerny I am on rails edge, and that seems to work

[jurikern]

Seems like a after_transition not works for rails edge (ActiveRecord) to ...

[amacneil]

+1

[schaary]

+1

[miry]

+1

[jurikern]

Last time authored 10 months ago and 19 unresolved pull requests. Very sadly ...

[edbo]

@obrie Would be a shame to see state machine go stale, I'm a big fan. Rails is now at v4.1.0rc2 which I reckon means we're pretty close to the release which will make this officially 'broken' soon.

I'm sure some people in the community would be happy to help with maintenance.

[richpeck]

Same problem in 4.1.0 stable

[patrickespake]

+1
Same problem in 4.1.0 stable.

[cryo28]

+1

[MirkoMignini]

+1

[saboyutaka]

+1

[klaut]

+1

[nhoffmann]

+1

[simonmd]

+1

[simonmorley]

👍

[awsmsrc]

guys just use AASM (Acts As State Machine), its a shame to see this one go but its had no activity for a while

[catmando]

word to the wise, while its great that somebody is supporting state_machine, it is not 100% the same behavior as the old state_machine gem... I suspect there were bugs in the old version that have been fixed. At any rate, you might find during the upgrade the quickest fix is the monkey patch.

[akonan]

+1

[sennor]

+1

[rvsingh]

+1

[droupou]

Thanks @the-teacher, and @gingermusketeer!