Thanks Tom. The crappy part is I'm not using memcache for anything at the moment.
Steve On Apr 8, 7:31 am, tomrossi7 <t...@themolehill.com> wrote: > Steve, > > Try throwing require 'memcache' in your environment.rb? I think that > is how I finally got around it... > > Thanks, > Tom > > On Apr 7, 11:19 pm, Steve Odom <steve.o...@gmail.com> wrote: > > > I'm having the same issue as Tom, but I'm not using Starling. I'm > > using spawn. I don't have anything in an initializer to wrap in a > > after_initialize. > > > Any ideas how to get workling to work in 2.3? > > > Steve > > > On Apr 7, 7:14 pm, Freddy Andersen <fre...@cfandersen.com> wrote: > > > > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > > > your Workling loader a after_init like so: > > > > config.after_initialize do > > > Workling::Remote.dispatcher = > > > Workling::Remote::Runners::StarlingRunner.new > > > end > > > > On Mar 20, 6:42 am, TomRossi7 <t...@themolehill.com> wrote: > > > > > One of the plugins I use is Workling. It throws the following error > > > > when I try to run it under 2.3: > > > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > > > > dependencies.rb:443:in `load_missing_constant': uninitialized > > > > constantMemCache(NameError) > > > > > The offending line is: > > > > > @@memcache_client_class ||= ::MemCache > > > > > I don't know a lot aboutmemcache, so I'm not sure what changed with > > > > 2.3 that could cause the error. Anyone have some ideas? > > > > > Thanks! > > > > Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
