As my CFFORM action has a coldfusion variable in it <cfform action="#script_name#?action=domains.default" method="POST" name="domainform">
A cfoutput is required. Otherwise what will happen is that the actual text "#script_name#" will be output instead of it's value. As I stated in another reply, I have tried moving the cfoutputs, and evenin getting rid of them altogether to see if that was the problem, and it wasn;t. Russ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 11 August 2005 13:45 To: CF-Talk Subject: RE: CFFORM error I understand that, but my point is I don't think you need the </cfoutput> AFTER the <cfform>. In any case, if moving it above <cfform> didn't solve the problem, then the typo is somewhere else in your code and we're not going to be able to help unless you can post all the code in the template AND maybe post your exact error message again (all of it). Dave -----Original Message----- From: Russ Michaels [mailto:[EMAIL PROTECTED] Sent: Thursday, August 11, 2005 8:32 AM To: CF-Talk Subject: RE: CFFORM error There is an opening cfouput in the code above the cfform (not posted as it's just a bunnch of cfsets and cfparams and comments), and I have tried moving the cfoutputs around as well. Russ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 11 August 2005 12:16 To: CF-Talk Subject: RE: CFFORM error ><cfform action="#script_name#?action=domains.default" method="POST" >name="domainform"> ></cfoutput> I looked through all your code and the only odd thing is the </cfoutput> just after the <cfform> I would move that ABOVE The <cfform> as I don't believe it's needed for the #script_name# to be evaluated since it's contained within a CF tag (CFFORM). And that's what could be causing yourp roblem. I don't see anything else wrong with it. If that's NOT it, then something else on your page is causing the problem and unless you post all the code, we will never be able to help you figure it out. Remember, sometimes, the CF error handler does NOT report the correct line where the error really is, but instead reports the line where it couldn't continue processing (which are not both always one and the same). Try moving the </cfoutput> above your <cfform> and if that doesn't work, then post your code at http://www.nomorepasting.com and let us know the pasting code and we will take a look at it and help you find the culprit....we have all banged our heads against our keyboards for times when it took us forever to find a simple typo that caused major headaches.... Dave **************************************************************************** ************** The information contained in this message, including attachments, may contain privileged or confidential information that is intended to be delivered only to the person identified above. If you are not the intended recipient, or the person responsible for delivering this message to the intended recipient, ALLTEL requests that you immediately notify the sender and asks that you do not read the message or its attachments, and that you delete them without copying or sending them to anyone else. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:214532 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
