>> 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
Very ODD.
The line of <cfreturn #result#> in the cfc should have been
<cfreturn true> since we don't need data back from the cfc.
and was previously <cfreturn true>. I've enabled the feature in FF.
case A, <cfreturn true>
ajax http post succeeds, RESPONSE: the {data} instead of TRUE ?????
case B, in the cfc, <cfset result="fielda, #fa#; fieldb, #fb#; memofield,#mf#">
<cfreturn #result#>
(just for the heck of it),
ajax http post succeeds, RESPONSE: just the #mf# instead of fielda, #fa#;
fieldb, #fb#; memofield,#mf# ?????
FYI, the computer is totally offline and wireless device driver was turned off
as well.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:325556
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
