tracker issue : CF-4060764

select a category, or use search below
(searches all categories and all time range)

[ANeff] Bug for: <cfpdf action="archive"..> fails for <cfhtmltopdf>-generated PDFs

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/ThirdParty

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 09/21/2015

Components: Document Management

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win XP All

Vote Count: 2

<cfpdf action="archive"..> fails for <cfhtmltopdf>-generated PDFs

This works:

cfdocument(format="pdf", filename=expandPath("./myPDF.pdf"), overwrite=true) {writeOutput("my PDF");}
cfpdf(action="archive", source=expandPath("./myPDF.pdf"), overwrite=true);

This fails:

cfhtmltopdf(destination=expandPath("./myPDF.pdf"), overwrite=true) {writeOutput("my PDF");}
cfpdf(action="archive", source=expandPath("./myPDF.pdf"), overwrite=true);

Error logged to pdfarchive.log:
"Information","ajp-nio-8016-exec-2","09/10/15","14:55:32",,"********PDFA Archive Conversion details for C:\path\to\myPDF.pdf. *********"
"Error","ajp-nio-8016-exec-2","09/10/15","14:55:32",,"PAGE ERROR"
"Error","ajp-nio-8016-exec-2","09/10/15","14:55:32",,"FONT ERROR"

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4060764

Bug Grouping Info:
Bug Group ID: BG175007
Bug ID: CF-4060764
Bug relationship: Awaiting Fix
Product: ColdFusion

Bug Group ID: BG175007
Bug ID: 4051255
Bug relationship: Pending Fix
Product: CT Gibson

Bug Group ID: BG175007
Bug ID: 4068740
Bug relationship: Awaiting Fix
Product: CT Gibson

External Customer Info:
External Company:  
External Customer Name: Aaron Neff
External Customer Email:



+1 ...........................
Vote by External U.
5802 | September 22, 2015 04:48:10 AM GMT
[added a bug group note CF-4060764 : ColdFusion : 11.0] : Gibson throws page error font error annotation error and some more even if conversion was successful. Logged a bug: 4068740 (Comment added from ex-user id:vadiraja)
Comment by Adobe D.
5792 | October 05, 2015 03:17:39 AM GMT
[added a bug group note CF-4060764 : ColdFusion : 11.0] : Hi Pooja, Thanks for logging 4068740, but I am unable to view it. Can you please make 4068740 viewable for commenting/voting? Thanks!, -Aaron
Comment by External U.
5793 | October 05, 2015 03:24:02 AM GMT
The internal team that we are dependent on for this fix has stated that they won't be fixing it. Hence, we are closing this bug
Comment by Kailash B.
5794 | July 21, 2017 05:45:47 AM GMT
Hi Kailash, Seriously!?!? A PDF gen'd via cfhtmltopdf can't be archived. And that team's just gonna say "nup, won't fix" and the CF Team is okay w/ that?? -Aaron
Comment by Aaron N.
5795 | July 21, 2017 07:04:37 AM GMT
And Adobe brags-up cfhtmltopdf as cfdocument's replacement - but it's not, for various reasons. cfdocument just can't be deprecated until cfhtmltopdf is up-to-part w/ cfdocument.
Comment by Aaron N.
5796 | July 21, 2017 07:28:25 AM GMT
Comment by Aaron N.
5797 | July 21, 2017 07:28:53 AM GMT
Currently this ticket's Status/Resolution/ReasonCode is Closed/Won't Fix/ThirdParty. Since the "ThirdParty" is actually just another Adobe team, the "ThirdParty" should be changed to "AnotherTeam". "ThirdParty" makes it sound like a fix for this ticket is outside of Adobe's control. When, in actuality, the fix is _within_ Adobe's control. The Acrobat Team should own this bug, and the CF Team shouldn't back down.
Comment by Aaron N.
5798 | July 21, 2017 09:03:19 AM GMT
I despair...
Comment by Carl V.
5799 | July 22, 2017 12:16:49 AM GMT
Hi Adobe, Per today's ColdFusion Developer Week webinar ("PDF enhancements in ColdFusion 2016"), this ticket is still awaiting a fix from Acrobat. Can you please change the State/Resolution/Reason to indicate the same? Currently it is "Closed/Won't Fix/ThirdParty". It should at least be "Closed/Deferred/ThirdParty". (even tho the Acrobat team isn't -completely- 3rd party ;)) Thanks!, -Aaron
Comment by Aaron N.
5800 | August 03, 2017 05:40:58 PM GMT
We are checking with the internal team to see if/when they plan to address this fix. Once we have the required information, we will change the status accordingly.
Comment by Vamseekrishna N.
5801 | August 07, 2017 02:26:23 PM GMT