Lucee 4.5.2 cfpdfparam difference with Adobe ColdFusion

Suppose the following on Lucee 4.5.2:

<cfset x = 1>
<cfdocument format="pdf" pagetype="A4" name="myVar#x#">
<cfdocumentsection>
Hi there
</cfdocumentsection>
</cfdocument>

<cfpdf action="merge" destination="RAM:///myPDF.pdf" overwrite="yes">
    <cfpdfparam source="#evaluate("myVar#x#")#" />
</cfpdf>

<cfcontent file="RAM:///myPDF.pdf" type="application/pdf">

then to check it also runs on Adobe Cf; you'd actually end up with:

"ByteArray objects cannot be converted to strings."
 
The original code for Adobe CF ran with the paramater like so: 

<cfpdfparam source="myVar#x#" />


Both sets of documentation list source defined as follows:
"Source PDF file to merge. You can specify a PDF variable, a cfdocument variable, or the pathname to a file."

This would indicate it is just a pointed type and that in Lucee it is not evaluating the string properly.

Just as an aside, while very messy, this will work:
<cfif server.coldfusion.productname eq "Lucee">
<cfpdfparam source="#evaluate("myVar#x#")#"">
<cfelse>
<cfpdfparam source="myVar#x#"">
</cfif>


As an aside, Lucee throws an error if the parameter syntax is like so:
<cfpdfparam source="#evaluate("myVar#x#")#""></cfpdfparam>

Comments

Post a Comment

Popular posts from this blog

Global SQL Procedure, System Objects and sp_ms_marksystemobject

You may come across a need to have a database of utils full of generic procedures which work on indvidual databases (say client databases). You can't pass the database name into the procedure as a parameter and say "use @dbname" in the procedure and dynamic sql sucks. One workaround is to create the procedure in the master database and then mark it as a system object. eg use [master] create procedure sp_doThis // note the sp_ prefix is required begin // etc etc end go exec sp_ms_marksystemobject 'sp_doThis' // second note, this procedure is undocumented, so I wouldn't be relying on this for life or death. use [myotherdb] exec sp_doThis go All done!
Read more

cf_sql_timestamp vs cf_sql_date vs getdate()

If there's one thing I don't like it is people confusing a date with a timestamp, and how a lazy bit of development can ruin a load of data. Here is a simple query inserting data to a timestamp I found in a system where all the created dates were truncated because of the incorrect syntax. Bad one which was in use: insert into testdate values (<cfqueryparam cfsqltype="cf_sql_date" value="#createodbcdatetime(now())#">); Result :  2015-09-29 00:00:00.000 Best One (easiest to read) insert into testdate values(getdate() ); Result : 2015-09-29 10:10:09.880 Not great (no binding) insert into testdate values(#createodbcdatetime(now())#); Result :  2015-09-29 10:14:44.000 What the bad one should have been insert into testdate values(<cfqueryparam cfsqltype=" cf_sql_timestamp " value="#createodbcdatetime(now())#">)
Read more

Tracking Events and Properties Naming Conventions and Best Practice

Tracking has 2 parts, the event and the properties of the event and captured together will tell you what users are doing. Data Step 1 Event Naming Best Practice: Object & Action in past tense with "Title Casing" and spacing, eg "Product Added" where Product is the Object and Added is the Action Data Step 2 Event Property: Be consistency, use nouns and use snake_case (just stay that way), and do not nest properties, most downstream providers can use nested properties. This is what tells us what people are doing on the event.  Data Step 3 As a further clarity and to avoid having hundreds of events, the event names should be generalized and then the properties should be used for specificity, else you could end up with lets say  Product Added from Contact Page Product Added from List Page Product Added from Recommendation Or  just "Product Added", with a property of say "source" Think an example like this:  Event Name "Product Added" Pr
Read more