Pluginaweek state_machine

Comments and changes to this ticket

• 

  Dennis Theisen August 7th, 2008 @ 04:34 PM

  It is also not possible for me to use

  
  Article.create
  

  anymore, it throws the same kind of exception:

  NoMethodError: undefined method create' for PluginAWeek::StateMachine::Event:Class</code>

  I am really going crazy over this, I have no clue what I am doing wrong. But it seems, like it's only me, as I have found no one else having this kind of problem... :(

• 

  Aaron Pfeifer September 7th, 2008 @ 01:35 AM

  • → State changed from “new” to “open”

  Hi soleone,

  Thanks for reporting the problem. It sounds like #create is getting called from within an event block like so:

  
  state_machine do
    event :do_something do
      create :id => 1 # or something like that
      ...
    end
  end
  

  Is this a problem you're still running into or has it since been resolved?

• 

  Dennis Theisen September 7th, 2008 @ 02:04 PM

  Hey Aaron,

  unfortunately I forgot to update this ticket, because the problem is resolved.

  There was a namespace clash: in our system we also had an Event class with a create() method, which was listening for Blogs and Comments creation. But somehow because the StateMachine's Event-Class was used in one of the child classes, whenever a Blog got created, it tried to call Event.create (of our Event class), but ended up calling StateMachine::Event.create - which obviously wasn't there.

  I fixed the problem by changing the Listener in our system from Event.create to ::Event.create

  Sorry for wasting your time, I thought I already updated this ticket.

  Greetings, Dennis

• 

  Dennis Theisen September 7th, 2008 @ 02:07 PM

  Btw, it seems I screwed up the layout because there is an unclosed code-tag. I tried to close it with this post :)

• 

  Aaron Pfeifer September 7th, 2008 @ 04:39 PM

  Thanks for the update. It turns out this actually is a problem which could affect other plugins here as well. I didn't think about the fact that including PluginAWeek::StateMachine in ActiveRecord would cause all model references to Event/Machine/Transition to point to those classes under the PluginAWeek::StateMachine namespace instead of the top-level namespace. A very interesting problem!

  A fix for this problem should be available within the next few days or so, at which point you should no longer need to use ::Event instead of Event :)

• 

  Aaron Pfeifer October 4th, 2008 @ 06:18 PM

  • → State changed from “open” to “resolved”

  (from [a3cbd3308f37deb083d277c1b253837e93e3407a]) Change how the base module is included to prevent namespacing conflicts [#1 state:resolved] http://github.com/pluginaweek/st...