In Docker, we were able to preconfigure a list of downloaded extensions (.lex files) and bring them into the lucee-server/deploy folder.
On startup, the extension would be loaded, and the current version would be set according to the loaded .lex file.
There's a regression in 5.3.7. That's not happening anymore.
We're running an old PDF extension as well as the following extensions:
MySQL version 8.0.19 (good)
Image Extension 188.8.131.52 (good)
PDF Extension 184.108.40.206-SNAPSHOT (BAD)
I’ll include a zip file so this can be reproduced.
you can still use the old engine, via this.pdf.type = "classic"; in application.cfc , or <cfdocument type=”modern|classic”> since
Oh! Another secret feature that’s mentioned nowhere in the docs or in cfdocument.
I’ll check this out and see if it works for our purposes.
I just added a note to the flying saucer page
the cfdocument page will be auto updated once a stable lucee release is published that includes the PDF extension version (220.127.116.11-SNAPSHOT) or newer
Thank you. I can confirm that using “classic” obviates this issue.
You can close this ticket if you want.
I also appreciate you updating the docs for this…there’s been a handful of things like this that I wished were in the docs. Sometimes in my code I have a references to an LDEV lucee issue in a comment, just to explain where I found, say this.tag.cfdocument.fontdirectory. Although the latter is in the docs now.
It's still a valid bug tho, you should be able to control which version of extensions you want to use. So we'll leave it open
glad I could help you out!
It's really easy to get involved to help improve the docs....