The thing is that if you have different engines the compiler might throw
errors. So what you can do is:
<cfif compareNoCase(server.coldFusion.productName,"BlueDragon")>
<cfinclude template="act_blueDragon_file.cfm">
<cfelseif compareNoCase(server.coldFusion.productName,"Coldfusion")>
<cfinclude template="act_cfmx_file.cfm">
<cfelse>
<cfinclude template="act_railo_file.cfm">
</cfif>
We do that quite often in order to solve incompatibilities or to make use of
improvements that are not part of other engines.
Greetings / Grüsse
Gert Franz
Customer Care
Railo Technologies GmbH
[EMAIL PROTECTED]
www.railo.ch
Join our Mailing List / Treten Sie unserer Mailingliste bei:
deutsch: http://de.groups.yahoo.com/group/railo/
english: http://groups.yahoo.com/group/railo_talk/
Matt Robertson schrieb:
>>> If you wrap the various different implementations in
>>> something like a CFIF around a CFINCLUDE, does that allow one
>>> (set of) templates to run on all engines ?
>>>
>> It very well might! I haven't tried, myself.
>>
>
> It works fine. Something old I snipped and simplified for the sake of
> illustration from some old code I have:
>
> <cfif not compareNoCase(server.coldFusion.productName,"BlueDragon")>
> ... do stuff ...
> <cfelse>
> ... do different stuff...
> </cfif>
>
> You can of course use different server variables, different values,
> snip out substrings etc. to make your decisions.
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Get the answers you are looking for on the ColdFusion Labs
Forum direct from active programmers and developers.
http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid-72&catid=648
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:292442
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
