>> I've moved on to an open source cfml engine >Don't ever do that. > >But seriously. First step of debugging ajax: install Firebug for Firefox if >you haven't already. Next, enable all the firebug console options for your >page and while viewing the console tab you should see your http post request >made by your proxy js object (when you fire that event). You will then be >able to examine the the data sent to your cfc and also the response. > >If there is no http request sent then the problem may well be with the >cfajaxproxy code - if a request *is* sent, then we can safely move on from >the client side code. > >With any luck, examining the http response will tell you exactly what's >going wrong and will be a cf / railo error page. > >HTH > >Dominic
Sorry, Dominic, I wasn't clear about the browser, the inline editing feature is IE specific, that is, Firefox has a hell time with it, hence, it's IE only, yes, I like Firefox's firebug and find it very helpful but not for this case. I have firebug lite set up for the IE7, but it didn't show http call etc. from cfajaxproxy as in FF/FB... more thoughts? thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325552 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
