I am pleased to annound the solution the the problem I described earlier, where
I was trying to call a JavaScript function via ajaxOnLoad and received only the
cryptic error message below, with no further details (and cfdebug did not
improve matters):
"Error processing Javascript in markup for element getTx: [Enable debugging
by adding 'cfdebug' to your URL parameters to see more information]"
The answer - which some people would abbreviate to RTFM - lay in my reading the
manual, and learning that it is simply not allowed to pass parameters via
ajaxOnLoad. Therefore, instead of the code <cfset ajaxOnLoad(txnx)>, where txnx
is either 'Tx' or 'Nx', I was forced to change the code to that below, where
each of the two JavaScript functions does nothing but call AddTranscript() with
the appropriate parameter.
<cfif txnx eq 'Tx'>
<cfset ajaxOnLoad('AddTranscriptTx')>
<cfelse>
<cfset ajaxOnLoad('AddTranscriptNx')>
</cfif>
Nonetheless, just like the situation where I was stuck earlier before I
discovered that the only way to pass parameters to a callback function is by
placing them inside the response coming back from the ajax-called page, this is
something Adobe's error-trapping behavior ought to catch right away as soon as
anyone tries it. In other words, ColdFusion.navigate(url, cfdiv,
callback(parm)) should result in a syntax error right away. And so should
<cfset ajaxOnLoad(parm)>. Hopefully CF 8.1 will have that enhancement.
Peyton
-------------------------------------------------------------
Annual Sponsor FigLeaf Software - http://www.figleaf.com
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------
