I found the problem, I'm fairly certain, Charlie.
In the cfc method that is processing the values, I had: <cfset session.values.section_subtitle = arguments.section_subtitle /> I figured I didn't need ## around arguments.section_subtitle. But when I surrounded all the argument values with '# #', such as '#arguments.section_subtitle#' , the ajax and method worked find. AJAX throws so many curves.it's hard to hit the ball! Thanks for responding. Rick From: jquery-en@googlegroups.com [mailto:jquery...@googlegroups.com] On Behalf Of Charlie Griefer Sent: Wednesday, April 08, 2009 4:05 PM To: jquery-en@googlegroups.com Subject: [jQuery] Re: Why won't these values work for an ajax function? view the source of the generated page and paste the mSaveSection() here. On Wed, Apr 8, 2009 at 1:01 PM, Rick Faircloth <r...@whitestonemedia.com> wrote: Here's the code: function mSaveSection() { datavalues = { dsn: '<cfoutput>#application.dsn#</cfoutput>', section_subtitle: '<cfoutput>#session.values.section_subtitle#</cfoutput>', section_text: '<cfoutput>#session.values.section_text#</cfoutput>' }; The application (or browser) just seems to "sit and spin" when this is run.no error, no timeout, nothing. When I look at the generated code in Firebug, the values are good for the session variables. And I use '<cfoutput>#application.dsn#</cfoutput>' successfully in all other ajax functions without problem. When I substitute hard-coded values in place of the session variables, the function works. Does anyone familiar with jQuery and ColdFusion session variables know of an issue with this approach? Thanks, Rick ---------------------------------------------------------------------------- ----------------------------------------------------------- "It has been my experience that most bad government is the result of too much government." - Thomas Jefferson -- I have failed as much as I have succeeded. But I love my life. I love my wife. And I wish you my kind of success.
