I am building a custom tag for auto emailing and I have gotten stuck at the actual generation of the email. You see right now my tag would accept any cfmail attribute available. The problem is that when I attempt to send the email with cfmail I need to use the attributes they ACTUALLY specified. I can't generate the attributes dynamically without generating a JIT error(ie:i cant loop through a list or collection and output them.) and I cant set them equal to form variables because some of them cannot be specified and set to nothing. Any ideas??
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Dynamic Generation of CFMAIL attributes
- Thread starter thysonj
- Start date
bhightower
Programmer
i use this custom tag to send me a message when the site breaks ...
here is the tag
*********************************************
<!--- Set Variable Defaults --->
<cfparam name="attributes.to" default="#request.adminEmail#">
<cfparam name="attributes.from" default="#request.adminEmail#">
<cfparam name="attributes.type" default="na">
<cfparam name="attributes.message" default="na">
<cfparam name="attributes.detail" default="na">
<cfparam name="attributes.TagContext" default="na">
<!--- Send Email Alert With Debug Info --->
<cfmail to="#attributes.to#" from="attributes.from" subject="Broken Report" type="HTML">
#attributes.Type#<br>
#attributes.Message#<br>
#attributes.Detail# <br>
<P>The contents of the tag stack are:</P>
<cfloop index = i from = 1 to = #ArrayLen(attributes.tagContext)#>
<cfset sCurrent = #attributes.tagContext#>
<BR>#i# #sCurrent["ID"]#
(#sCurrent["LINE"]#,#sCurrent["COLUMN"]#)
#sCurrent["TEMPLATE"]#
</cfloop>
</cfmail>
****************************************
and i call it like so....
<cfcatch type="any">
<cf_email_warning to="#request.adminEmail#" type="#cfcatch.Type#" message="#cfcatch.Message#" detail="#cfcatch.Detail#" TagContext="#cfcatch.TagContext#">
<cflocation url="#request.errorPage#" addtoken="no">
</cfcatch> ------------------------------------------------------------------------------
brannonH
if( !succeed ) try( );
here is the tag
*********************************************
<!--- Set Variable Defaults --->
<cfparam name="attributes.to" default="#request.adminEmail#">
<cfparam name="attributes.from" default="#request.adminEmail#">
<cfparam name="attributes.type" default="na">
<cfparam name="attributes.message" default="na">
<cfparam name="attributes.detail" default="na">
<cfparam name="attributes.TagContext" default="na">
<!--- Send Email Alert With Debug Info --->
<cfmail to="#attributes.to#" from="attributes.from" subject="Broken Report" type="HTML">
#attributes.Type#<br>
#attributes.Message#<br>
#attributes.Detail# <br>
<P>The contents of the tag stack are:</P>
<cfloop index = i from = 1 to = #ArrayLen(attributes.tagContext)#>
<cfset sCurrent = #attributes.tagContext#>
<BR>#i# #sCurrent["ID"]#
(#sCurrent["LINE"]#,#sCurrent["COLUMN"]#)
#sCurrent["TEMPLATE"]#
</cfloop>
</cfmail>
****************************************
and i call it like so....
<cfcatch type="any">
<cf_email_warning to="#request.adminEmail#" type="#cfcatch.Type#" message="#cfcatch.Message#" detail="#cfcatch.Detail#" TagContext="#cfcatch.TagContext#">
<cflocation url="#request.errorPage#" addtoken="no">
</cfcatch> ------------------------------------------------------------------------------
brannonH
if( !succeed ) try( );
csteinhilber
Programmer
> The problem is that when I attempt to send the email
> with cfmail I need to use the attributes they
> ACTUALLY specified.
I'm not exactly sure what you're asking... but it sounds like you're having a common problem.
You certainly CAN generate attributes dynamically... if you need to create a to: attribute out of a list of addresses, you create the list first:
If you need to send cc:s or bcc:s depending on a given set of circumstances (ie - only send a cc if a given option is selected), you have to use CFMAILPARAM rather than CFMAIL's built in cc parameter since CFMAIL doesn't like it when you pass cc or bcc an empty string.
-Carl
> with cfmail I need to use the attributes they
> ACTUALLY specified.
I'm not exactly sure what you're asking... but it sounds like you're having a common problem.
You certainly CAN generate attributes dynamically... if you need to create a to: attribute out of a list of addresses, you create the list first:
Code:
<CFSET myAddressees = ""
<CFLOOP ... whatever>
<CFSET myAddressees = ListAppend("#myAddressees#",anotherAddress)>
</CFLOOP>
<CFMAIL to="#myAddressees#" ...>If you need to send cc:s or bcc:s depending on a given set of circumstances (ie - only send a cc if a given option is selected), you have to use CFMAILPARAM rather than CFMAIL's built in cc parameter since CFMAIL doesn't like it when you pass cc or bcc an empty string.
Code:
<CFMAIL to="#myAddressees#" ...>
<CFIF needToSendCC EQ true>
<CFMAILPARAM name="Cc" value="someaddress@somedomain.com">
</CFIF>
:
:
</CFMAIL>-Carl
- Thread starter
- #4
My problem is this exaclty..
Say when I call the tag I want to specify a BCC. Keep in mind they do not have to. Eventually I will need that in the cfmail. It is easy just to have that parameter(BCC) in cfmail and set it to attributes.bcc. Where the problem is when they don't specify that. Then I have a cfmail tag that expects a bcc attribute that doesn't exist. I need to be able to create the parameters dynamiclly depending on what they do specify. If they set a type then it puts the type parameter in the cfmail tag and sets it to attributes.type. But if they don't specify the type then the type parameter needs not be put in the cfmail tag. Actually when it comes to cc.bcc.type etc...this has not been a problem because they CAN be empty. Where the biggest propblem is with parameters like query and startrow that cannot be empty.
Say when I call the tag I want to specify a BCC. Keep in mind they do not have to. Eventually I will need that in the cfmail. It is easy just to have that parameter(BCC) in cfmail and set it to attributes.bcc. Where the problem is when they don't specify that. Then I have a cfmail tag that expects a bcc attribute that doesn't exist. I need to be able to create the parameters dynamiclly depending on what they do specify. If they set a type then it puts the type parameter in the cfmail tag and sets it to attributes.type. But if they don't specify the type then the type parameter needs not be put in the cfmail tag. Actually when it comes to cc.bcc.type etc...this has not been a problem because they CAN be empty. Where the biggest propblem is with parameters like query and startrow that cannot be empty.
csteinhilber
Programmer
As I said... the solution is to use CFMAILPARAM tags, rather than the attributes of the CFMAIL tag itself:
-Carl
Code:
<!--- don't put cc= or bcc= in the CFMAIL tag --->
<CFMAIL to="#myAddressees#">
<CFIF needToSendCC EQ true>
<CFMAILPARAM name="Cc" value="someaddress@somedomain.com">
</CFIF>
<CFIF needToSendBCC EQ true>
<CFMAILPARAM name="Bcc" value="someotheraddress@somedomain.com">
</CFIF>
:
:
</CFMAIL>- Thread starter
- #6
- Thread starter
- #7
csteinhilber
Programmer
Grrrr... you're right thysonj... so sorry for leading you down that path. Apparently "Cc" and "Bcc" are actually false headers. A mail client actually interprets these and sticks them into a RCPT TO header before it sends the mail.
My bad.
However, here's a second solution to make it up to you ;-)
Not terribly pretty, but it works.
-Carl
My bad.
However, here's a second solution to make it up to you ;-)
Code:
<CFSAVECONTENT var="emailBody">
#attributes.Type#<br>
#attributes.Message#<br>
#attributes.Detail# <br>
<P>The contents of the tag stack are:</P>
<cfloop index = i from = 1 to = #ArrayLen(attributes.tagContext)#>
<cfset sCurrent = #attributes.tagContext#>
<BR>#i# #sCurrent["ID"]#
(#sCurrent["LINE"]#,#sCurrent["COLUMN"]#)
#sCurrent["TEMPLATE"]#
</cfloop>
</CFSAVECONTENT>
<CFIF IsDefined("cclist") and Len(Trim(cclist)) GT 0>
<CFIF IsDefined("bcclist") and Len(Trim(bcclist)) GT 0>
<CFMAIL to="#tolist#" cc="#cclist#" bcc="#bcclist#">
#emailBody#
</CFMAIL>
<CFELSE>
<CFMAIL to="#tolist#" cc="#cclist#">
#emailBody#
</CFMAIL>
</CFIF>
<CFELSE>
<CFIF IsDefined("bcclist") and Len(Trim(bcclist)) GT 0>
<CFMAIL to="#tolist#" bcc="#bcclist#">
#emailBody#
</CFMAIL>
<CFELSE>
<CFMAIL to="#tolist#">
#emailBody#
</CFMAIL>
</CFIF>
</CFIF>Not terribly pretty, but it works.
-Carl
- Thread starter
- #9
While i think your second solution would surely work it unfortunately is not an option here as I am trying to allow users to specify any of the 16 params avaiable to cfmail. setting up if else statements with that many options presents far too many permutations for practical use. I believe i am simply up a creek as they say and will need to redefine the functionality i want to offer.
Thanks for the help though.
Thanks for the help though.
- Status