|
Brad
|
June 22, 2018 at 12:57 pm
When downloading an Order Confirmation PDF, I am getting boxes that appear in the document as if there is a placeholder for an image. Is there an option that I need to check or am I missing some EE assets?
Thanks!
|
|
Tony
|
June 22, 2018 at 1:34 pm
Hi Brad,
May I ask where you got your thread title from?
The reason I ask is we set DOMPDF_ENABLE_REMOTE to true – http://take.ms/MCGlf
Can you link me to either an event I can run a test registration on, or add a link to a test registration’s order confirmation here so I can view the problem?
Generally, the cause is either allow_url_fopen has been disabled on your site or your messages were set up using EE4 Decaf and you’ve upgrade to the regular version, so now your template is using the EE4 decaf directory for the images and needs to be updated.
|
|
Brad
|
June 22, 2018 at 1:55 pm
Hi Tony,
Thanks for your response. I used the small text that is near each placeholder on the pdf to generate the title.
Here is a link to do a test registration:
https://springhill.cc/ministries/women/
I have attached the pdf so you can take a look at it too.
There is a great possibility that way back when, I originally started with EE4 Decaf and then upgraded but I don’t really recall.
Please let me know if you need anything else. Thanks again for your help.
Brad
|
|
Tony
|
June 22, 2018 at 4:50 pm
Thanks for your response. I used the small text that is near each placeholder on the pdf to generate the title.
Hmm, yeah I see. That changes things.
Do you have another plugin that generates PDFs? It looks like something is loading DOMPDF before EE does (EE checks if a version has loaded before loading its own), but the things is, nothing should be loading DOMPDF on that request other than EE.
There is a great possibility that way back when, I originally started with EE4 Decaf and then upgraded but I don’t really recall.
That’s not the issue, your images are using the regular directory path.
|
|
Brad
|
June 26, 2018 at 8:11 am
Tony,
I found that the pdf add-on for our Ninja Forms Plugin is causing the problem with the DOMPDF. What is the appropriate way to move forward with this? Should I contact Ninja Forms and inform them of the conflict with EE4? Or is this something you want to look at on your end? We use Ninja Forms for all of our forms outside of event registrations and the ability for it to generate pdf’s of the submissions is important. What do you suggest? Thanks!
|
|
Tony
|
June 26, 2018 at 9:37 am
Hi Brad,
I’m assuming you are using the PDF Form Submissions add-on for Ninja forms?
This one – https://ninjaforms.com/extensions/pdf-form-submissions/
If so can you send me a copy of the add-on so I can take a look? You can send a copy to support[at]eventespresso.com (you may need to host the .zip and include a link to download in the email depending on the filesize)
|
