Thanks Jeff.

Sorry, I should have been more specific.  I had added <cfset
request.mode.ajax = true /> to _serverSpecificRequestScope.cfm.  This
removed the issue all together and the site functions fine.

I can narrow the issue down to using the <skin:htmlhead..> tag.  We
are using the cfUniform library for some forms and add the js & css
calls to AJAX libraries to the <skin:htmlHead...>.  We were cautious
to make sure there were no duplicate calls to already cached AJAX
libraries from FC.

Thank you,
Michael


On Dec 8, 9:30 am, Jeff Coughlin <[email protected]> wrote:
> The error is a bit misleading.  I'm not sure exactly why it happens.  It's as 
> if the variable didn't exist when your application.cfc's onError() method was 
> called.
>
> What I can say is that in most cases the error is happening because you have 
> a bug in your project code somewhere.  The error then trigger's your 
> onError() method thus causing the chain of events.  For a temp fix, what I 
> usually do is manually edit my project's _serverSpecificRequestScope.cfm and 
> temporarily set the following (anywhere in that file): <cfset 
> request.mode.ajax = true />.  Run the page in question again and see what 
> "real" CF error is happening (most likely a bug in your project's code 
> somewhere).  After you've fixed the bug, remember to remove (or comment) the 
> change you made in _serverSpecificRequestScope.cfm.
>
> Regards,
>
> --
> Jeff Coughlin
> Web Application Developerhttp://jeffcoughlin.com
>
> On Dec 8, 2010, at 9:21 AM, MJ wrote:
>
> > I have recently noticed an error message of " Element MODE.AJAX is
> > undefined in REQUEST. " popping up on site's running FC5 and FC6.0.7
> > in CF9. Under CF8 this did not occur.  This error occurs on either the
> > webtop or the front end and happen mostly (albeit not all the time)
> > with an updateapp.  Since the core has not been altered, nor the skins
> > on the sites I have to assume I have an issue in CF9's setup.  Does
> > anyone have any thoughts on CF9 tuning tips or perhaps a config in FC
> > itself to shunt this issue?
>
> > Thank you!
> > Michael
>
> > --
> > You received this message cos you are subscribed to "farcry-dev" Google 
> > group.
> > To post, email: [email protected]
> > To unsubscribe, email: [email protected]
> > For more options:http://groups.google.com/group/farcry-dev
> > --------------------------------
> > Follow us on Twitter:http://twitter.com/farcry

-- 
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: [email protected]
To unsubscribe, email: [email protected]
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry

Reply via email to