|
Kylee
|
November 29, 2015 at 6:30 pm
Hi I’ve noticed that when I click the button to download my PDF (invoice and receipt), the words Tax Invoice, date and transaction number don’t appear in the right corner. That section is blank. It works when I just click the link but as soon as I create the PDF, it disappears. Do you have any idea why that would be?
Thanks
Kylee
|
|
Tony
|
November 30, 2015 at 2:30 am
Hi Kaylee,
I placed a test registration onto one of your events and can see the section disappears but I can’t see any reason for it.
DOMPDF (which is the library EE uses to build the PDF’s) is much more ‘fussy’ on the HTML being valid, your browser will usually do its best to display the content even if the format is incorrect. DOMPDF will simply fail.
Within your Invoice message template, switch to text mode and double check your HTML is correct.
DId you create a custom template or edit the global one?
|
|
Kylee
|
December 1, 2015 at 3:54 pm
I did just edit the original template but I know now that I should create a custom one instead. So I will create the custom template, reset the receipt back to the original code, make my new custom one the default and then check out the original receipt code to see which might bit be causing the issue because I’ve changed too much of it. I did take out the “switcher” button as that doesn’t really make sense in my context. It’ll just confuse them. I’ll reply if I don’t resolve the problem by doing the above.
|
|
Tony
|
December 1, 2015 at 5:20 pm
Really it depends on the use case.
You can edit the global template, but then to confirm if its an issue with modifications you would need to create a new custom template, reset that template, assign it to an event and confirm if that ‘default custom template’ worked as expected.
The global template is used by all of your events by default, custom templates need to be assigned on a per event basis, so if you want all your events to use this new template, you would edit the global.
So if you want to create a custom template from your current global, then reset the custom template and assigning it to an event you can then test if the default works as expected and we can investigate from there.
|
