Thanks Swartz, Before I started to develop the extension, I upgraded radiant from 0.7.1 to 0.8.2. I just tried creating a brand new radiant 0.8.2 instance, copied the extension I've been working on and the problem went away.
The 0.7.1 instance had frozen gems before upgrading to 0.8.2, at which point I refroze the gems. I ran all the migration and update scripts for radiant and for the extensions I upgraded. Not sure where to start looking for typos. I'm guessing it would have to be in one of the extensions I'm using. Any ideas on an easy way to find a potential typo? On Wed, Oct 6, 2010 at 10:37 AM, swartz <netv...@gmail.com> wrote: > I had a similar issue when I was moving extensions from dev-server to > production. > One of the issues was that I had a typo in the migration scripts and > one of the table fields was misnamed when migration was executed. So > when I attempted to retrieve data from it, it had that same error > regarding "match" method. > > Another issue I ran into is when in one of my models (Subscriber) I > specifically refer to another model (like Role.all) either through a > conditions hash in a named_scope or via a custom validation rule. > > Just my experience. > > Check the lines from your code that the error log refers to. That > should give you a good idea what went wrong.
