Missing ddx processing after upgrade to ColdFusion 2021

[Peter Kulla]

Hello Experts,

I’ve been succesfully running an application on CF2016 Standard which manipulates PDF files using the <cfpdf action="processddx" …> tag (adding some header / footer / watermark).

After migrating the server to CF2021 everything works as expected under Developer License.

As soon as I register the CF2021 Standard license the DDX processing gets ignored and PDF files remain unchanged. This behavior is reproducible by switching between the "dveloper" and "Standard" license key.

Has anybody else encountered this issue?

I wonder whether it is just a bug or a change in the license policy? And if so, where it has been announced - i didn't find any hints on the Adobe website.

Thanks a lot,

Peter

[Dave Watts]

I would just open that as a support ticket right away. I suspect it's been excluded by accident, and most people don't use DDX so it just hasn't been discovered yet!

Dave Watts, Eidolon LLC

[kristi31067556]

Hello Peter,

I am having the same problem now in ColdFusion 2021 Standard. When we migrated from CF 11 to 2021 the "isDDX(#myDDXstring#)" function now returns a value of FALSE. My DDX file could not be more simple but nothing I do with it will pass the isDDX() test.

Did you ever find a solution to this problem, and if so, would you please share it with me?

Thank you!

Kristi

[Peter Kulla]

Hello Kristi,

well, it is more than 2 years ago... at that time (CF2021, update level 0) I've been given a Patch from Adobe support. But as far as I can tell, the fix was later included in Update 1 or Update 2. Since then I did not encounter any more problems with DDX.

However building a correct DDX string can be a little bit tricky - are you sure, it worked with CF11 before the migration?

[Charlie Arehart]

Kristi, I can confirm seeing the same behavior change in cf2021. I have created a bug report, with sample code and links to it on both cfiddle.org and trycf.com. The former runs cf enterprise and works, while the latter runs the free Developer edition and fails (on '21 but not' 18).

(I realize your question was about Standard, but if they changed it in '21 to not even run on Developer, that's why it also would not run on Standard).

Add a vote there, and any comments:

https://tracker.adobe.com/#/view/CF-4217953

Note that I also pointed them to this thread, and your first comment here from yesterday. 

[BKBK]

+1

voted

[Charlie Arehart]

Kristi, do you find the problem still to happen? If you had not added a vote on that bug report, you may not realize that in August Adobe closed the bug ticket I had filed, saying they were not able to reproduce the error.

Somehow I did not get a notification that day, but I have to admit that I now no longer do get the error, though I did when I filed the bug report.