Found it.
Turns out I had the old timed_fragment_cache plugin residing in the
code, and though I wasn't actually using it anywhere in my current
codeline ... it was still being loaded.
I found a fix for timed_fragment_cache at ruzee.com (http://
www.ruzee.com/blog/2008/07/timed_fragment_cache-on
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 th
_erbout is used ALL over the place (e.g. capture blocks), so it's
probably like what Josh says..
On Sat, Jan 31, 2009 at 8:08 PM, Josh Ferguson 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
> st
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
> 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 relate
