rubyonrailsin

Colin Law wrote:
> On 31 March 2010 16:33, Jeremy Woertink <lists@ruby-forum.com> wrote:
>>>>>> l.name = "test"
>>>>> a <=> b
>>>>> 5 <=> 4
>>
>> Yeah, that much I'm certain of. The only thing I don't know is maybe if
>> cache-money does something with that when trying to save an object and
>> throwing it into cache.
>>
>> This all works perfectly fine on my local machine, just not on the
>> production server. So I figure it's some gem that only does certain
>> things in production. I'm using Geokit too, so if anyone knows of any
>> issue with either of these gems that might cause something like this,
>> please let me know.
>
> Can't you see from the trace where it is failing?
>
> Colin

Yeah, I looked through the trace, and it was nothing but all these
cache-money calls. I figured it out though, had nothing to do with
cache-money. It was Geokit. I just started commenting out lines until it
worked, and taking out acts_as_mappable seemed to have fixed it >.< I'm
sure this is a "hack" solution because it doesn't make sense at all.
Thanks for the help guys!

~Jeremy
--
Posted via http://www.ruby-forum.com/.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.