Hey John/Michael,

Thanks for the hints.  I'll try and tack it down some more so.  I've a
ways to go before such issues become second nature.

As long as I can be assured that it's not infact a core issue, just a
clash with something on my end, I'll spend more time looking into it.

I'll update this thread if/when I can track it down.

Thanks.

On Feb 1, 4:08 am, Josh Ferguson <[email protected]> wrote:
> We saw something like this when we had a version of erubis being  
> required in tucked away corner of one of our initializers, check for  
> stuff like that as well.
>
> Josh Ferguson
>
> On Jan 31, 2009, at 6:00 PM, Michael Koziarski wrote:
>
>
>
> >> I'd appreciate any help on how to correct it or work around it ...
> >> short of yanking fragment caching from the app.
>
> > I'm using fragment caching on a 2.2.2 app and not seeing this problem,
> > and given the nature of your error message I'm guessing it's an old
> > plugin.
>
> > Do you have any plugins related to caching or template languages?
> > Have they been updated for 2.2.2?  What does the rest of the
> > stacktrace say?
>
> > --
> > Cheers
>
> > Koz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to