|
motio
|
March 28, 2018 at 9:29 am
The system creates an PDF Invoice. I was wondering if I could use something of it to make a custom PDF somehow.
Right now we export the csv report and use a word template with variables of the csv report to make PDFs/prinouts, e.g. Certificates or Documentation for an event. This workflow doesn’t cost that much time, but for 100 events a year it is time that I could save.
|
|
Josh
|
March 28, 2018 at 10:10 am
Hi Thomas,
Event Espresso 4 actually uses the bundled third-party library (DOMPDF) to convert the html invoice into a PDF. In order to use DOMPDF you’d need to start with an html file, so it would not be a straight conversion from a .csv file.
|
|
motio
|
March 28, 2018 at 10:20 am
Okay. For that I wouldn’t need a csv because I would have the final document.
So I cloud also use a plugin like “DK PDF” for that http://wp.dinamiko.com/demos/dkpdf/.
|
|
Josh
|
March 28, 2018 at 10:21 am
No because that particular plugin converts WP posts into PDFs.
|
|
motio
|
March 28, 2018 at 10:29 am
Now I understand. I have to build a template html, that DOMPDF know where to put the variables. Where do I find the html for the invoice? I would like to use this as a template.
My idea with the plugin was to create a private wordpress page and fill that with information from a custom table template (template_file in the Table view Add-on).
|
|
Josh
|
March 28, 2018 at 10:43 am
The html for the invoice can be found by going to Event Espresso > Messages > Default Message Templates > Invoice.
|
|
motio
|
March 29, 2018 at 2:37 am
I thought that I went through every setting but missed the possibility to change the html template. Thank you for that. That could be a great solution for the certificate after the event. We have to display the attendance in the certificate.
I haven’t found the the check-ins/attendance of the attendees. I understand that you don’t need that at the beginning of an event. Is there a hook to add that as a shortcode?
|
|
Josh
|
March 29, 2018 at 7:32 am
There are two hooks, one for registering the new shortcode:
FHEE__EE_Shortcodes__shortcodes
and the other for returning the parsed content:
FHEE__EE_Shortcodes__parser_after.
|
