state :forgetful, :enter => :do_forgot_password

def do_forgot_password
make_password_reset_code
UserMailer.deliver_forgot_password(self)
end

@dkmenace -
I’ve been using acts_as_state_machine with 2.0.2 and Edge and haven’t had problems.

>> person = Person.new
=> #<Person id: nil, state: nil, created_at: nil, updated_at: nil>
>> person.shower!
NoMethodError: You have a nil object when you didn’t expect it!

But,

>> person.state = ‘working’
=> “working”
>> person
=> #<Person id: nil, state: “working”, created_at: nil, updated_at: nil>
>> person.shower!
=> true
>> person
=> #<Person id: 3, state: “sleeping”, created_at: “2008-03-11 15:04:41″, updated_at: “2008-03-11 15:04:41″>

It’s still sleeping in the end! So what I understand is that it doesn’t matter what you do until the record is saved. It will still be initialized like it is defined no matter what events you call before.

I guess in the end it’s not good setting the default value through migrations like you say in the article. It will not matter when it is saved.

Good day.

Here are some intricacies I believe I cannot describe well:

>> person = Person.new
=> #
>> person.shower!
NoMethodError: You have a nil object when you didn’t expect it!

But,

>> person.state = ‘working’
=> “working”
>> person
=> #
>> person.shower!
=> true
>> person
=> #

It’s still sleeping in the end! So what I understand is that it doesn’t matter what you do until the record is saved. It will still be initialized like it is defined no matter what events you call before.

I guess in the end it’s not good setting the default value through migrations like you say in the article. It will not matter when it is saved.

Good day.

To Dave: Good point! I think it’s not good having just an empty array as the transition is not allowed. Any idea how to patch it in a separate “file” / plugin? (I’m very new to rails, so sorry for that “stupid” question.)

Greetz,
Chris

For example:

state :fooish
state :barish
state :bazish

event :bar do
transitions :from => :fooish, :to => :bar
end

something.state = ‘baz’
something.bar! #=> []

A quick monkey patch would overload Event::fire(record):

def fire(record)
next_states = next_states(record) # line added
return false if next_states.empty? # line added
next_states.each do |transition| # line edited
break true if transition.perform(record)
end
end

something.state = ‘baz’
something.bar! #=> false

D

This plugin maps a finite state machine. I think you should draw out your state diagram first and see how you want to transit from one state to another. You sound as if you want to have multiple initial states. Things should be much clearer with a state diagram. Hope this helps.