Now if you run this code, you'll find that it works just fine as one template. Somehow my request scope is not making it to the tag called at the bottom. I've used dumps to confirm this. I thought that was the whole point to the Request scope. Why is it doing that?
And I think that the fact that there is including and tagging going on
<!--- Now in my base template --->
<!--- Now including a header template to set some vars and copy the session structure --->
<cflock scope="session" type="exclusive" timeout="3">
<cfscript>
if (not isdefined("session.dr")) {session.dr = structnew();}
session.dr.formpage = "q_p_d_download.cfm";
session.dr.actionpage = "q_p_d_downloadp.cfm";
session.dr.resultspage = "q_p_d_downloadr.cfm";
</cfscript>
</cflock>
<cflock scope="session" type="readonly" timeout="3">
<cfset request = duplicate(session)>
</cflock>
<!--- include is now done --->
<h2>Download Request</h2>
<p>
Fill in the applicable information below to receive your download.
</p>
<!--- now calling a tag with an attribute: id=1 --->
<cfparam name="attributes.id" default="">
<h4>Your Information</h4>
<!--- the next line is the line that errors, saying: Error resolving parameter REQUEST.DR.ACTIONPAGE The object DR.ACTIONPAGE is not present in the scope named REQUEST. --->
<form name="form1" action="<cfoutput>#request.dr.actionpage#</cfoutput>" method="POST" onsubmit="return check();" >
-- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
