Support

March 26, 2018 at 3:04 am

Hi Darrell,

The links for your icons are using decaf:

/wp-content/plugins/event-espresso-decaf/core/

Your site currently has the regular version of EE installed so those paths aren’t valid.

I’m guessing you installed decaf first and then upgrade to regular, what happens with the above is decaf sets up the message templates and then saves them to the database (meaning the above URL’s use the decaf directory), then when you switch to regular those URls need to be altered.

If you have not modified the Receipt template the quickest way to fix is to go to:

Event Espresso -> Messages -> Default message templates -> Receipt.

In the side bar you’ll see a ‘reset templates’ button, click that and EE will regenerate the Receipt using the correct path.

If you’ve edited the templates, don’t click that button as you’ll need to update the links manually. Set all of the editors to text mode and do a search in your browser for ‘event-espresso’ – http://take.ms/OKBS0

You’ll find 4 references, 1 in EVENT_LIST and 3 in TICKET_LIST.

Update those from event-espresso-decaf to event-espresso-core-reg and save and retest.

March 26, 2018 at 3:43 am

Should I have done these steps as well:

No, thats only if you have not reset the template.

You get exactly the same error as above when downloading the PDF?

Can you link me to a Receipt for a test registration so I can view this?

March 26, 2018 at 4:34 am

Ok, that’s not the same error, notice how the links now show the correct path (and work in HTML) – http://take.ms/G2Ebi

Usually when this happens it’s because either your host has allow_url_fopen disabled on the server which is required by DOMPDF to pull the images (you’ll need to contact them and confirm this), or if you have iThemes security you’ll need to disable the “Enable HackRepair.com’s blacklist feature” within iThemes Security Pro.

March 28, 2018 at 2:24 am

It’s not just the icons, it’s basically an ‘external’ file used to generate the PDF’s but by external I don’t mean hosted on another server, any file that needs to be included within the main content (CSS, images etc) will all use allow_url_fopen within DOMPDF.

That means that even if you removed the images, your Invoice’s will not look the same as the HTML view as the CSS files can’t be used etc.

We do support CURL as an alternative to url_fopen. Your plugin author should know if they are using these functions or not.

Whilst that would be great if it was our own code, it’s not, it’s an external library we use that is specifically for generating PDF’s. Rewriting/creating our own library specifically for this task is not something we are considering as it’s a huge project in itself with little benefit when it’s already been created.

In short, if your host will not enable the above functions you either can’t use the PDF functions unless you are happy with the unstyled versions, or will need to move hosts.

March 28, 2018 at 2:36 pm

You can disable the PDF functions by going to Event Espresso > Messages > Settings, then click PDF, then move the toggle switch to the left, which turns off PDF.