function tikiOtinga(required string s required numeric i){
writeDump(arguments);
}
structCopy() bug
structCopy(). There's a bug been raised about it not working on ColdFusion scopes, which Adobe don't quite seem to be able to understand. The ticket is 3815793.
<cfchart> / <cfchartseries> bug details for Adobe & Railo
<cfexit> bug I thought I had spotted: solved
<cfexit> wrong, or am I misunderstanding?".<cfexit> is right. However there's still a bug in ColdFusion...<!--- testusingCfimport.cfm --->
<cfimport taglib="." prefix="t">
<t:basic>
Text within tags<br>
</t:basic>
<hr>
<t:basic exitMethod="exittag">
Text within tags<br>
</t:basic>
<hr>
<t:basic exitMethod="exittemplate">
Text within tags<br>
</t:basic>
<hr>
<!--- basic.cfm --->
<cfparam name="attributes.exitMethod" default="">
executionMode: <cfoutput>#thisTag.executionMode#</cfoutput><br>
<cfif thisTag.executionMode EQ "start">
<cfif len(attributes.exitMethod)>
exitMethod: <cfoutput>#attributes.exitMethod#</cfoutput><br>
<cfexit method="#attributes.exitMethod#">
<cfelse>
exitMethod: not specified<br>
<cfexit>
</cfif>
</cfif>
<cfexit> wrong, or am I misunderstanding?
each() function in each of Railo and ColdFusion
writeLog(), throw() and writeDump() aren't actually functions. Or aren't implemented properly if they are.
The information requested is not foundMy expectation is that all of them say "not found". Do any work properly for you?
allowedextforinclude functionality has changed. But the docs haven't been
compileextforinclude, by the time ColdFusion 11 was actually released).[...]out of the box ColdFusion 11 will only allow the inclusion of CFML and HTML files. Why? They cite "for security reasons". Here's a quote (posted in the bugtracker, originally from the pre-release forums):OK, I disagree there's merit in this, some others agree, others disagree. But... so be it. I actually thought - if I was in a charitable mood - that the people that were "for" this change made a reasonable case for its inclusion, so - whilst not agreeing with them - I was content to just shrug and go "yeah, oh well".
"Vamseekrishna Manneboina: Yes, this was done as part of a security measure. You can now only include CFM/CFML files by default. You can specify additional extensions via a property called allowedextforinclude in neo-runtime.xml. By default, HTM and HTML file extensions are already added to this list/property, thereby allowing for inclusion of HTM and HTML files too by default."