|
beresponsive
|
March 3, 2016 at 10:05 am
I get the following error when clicking on “View Full Order Confirmation Receipt”:
Warning: getimagesize(https://mounttraber.org/wp-content/uploads/2016/02/mtbc-2016-200px.png): failed to open stream: HTTP request failed! HTTP/1.0 403 Forbidden in /home/mtbcns/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Transaction_Shortcodes.lib.php on line 318
As per similar issues in the forum, I checked and allow_url_fopen is on.
When I click on the “Download PDF” button, I get this error:
Warning: getimagesize(https://mounttraber.org/wp-content/uploads/2016/02/mtbc-2016-200px.png): failed to open stream: HTTP request failed! HTTP/1.0 403 Forbidden in /home/mtbcns/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Transaction_Shortcodes.lib.php on line 318
Unable to stream pdf: headers already sent
Please let me know if there’s a solution. Thanks!
|
|
Josh
|
March 3, 2016 at 10:17 am
Hi there,
Do you happen to have the iThemes security plugin installed or even installed previously on this site?
|
|
beresponsive
|
March 3, 2016 at 10:18 am
Hi Josh,
Yes, iThemes Security is installed on the site.
|
|
Josh
|
March 3, 2016 at 11:06 am
One option you have is host your logo image file elsewhere. You can change the Logo Image setting in Event Espresso > Payment Methods > Invoice to use an image URL that’s hosted by Dropbox or some other server. If you don’t have a logo image set there, it will try to load the logo image that’s set in Event Espresso > General Settings.
What happens is iThemes security adds things to your server’s .htaccess file that can affect things like trying to open a file from the wp-content folder. Your other options are to not use a logo image on the invoices, or try contacting iThemes security to see if they can guide you on how to edit the .htaccess file. It’s probably a lot simpler to just set the logo image to get served from another server.
|
|
beresponsive
|
March 3, 2016 at 12:37 pm
Hi there, removing the image fixes these errors but causes errors within the PDF as it must be blocking images used within the PDF. I have contacted iThemes support to see if they can help resolve this so the PDFs look correct.
|
|
beresponsive
|
March 3, 2016 at 1:59 pm
The solution was to disable “Enable HackRepair.com’s blacklist feature” within iThemes Security Pro.
|
