Posted: September 5, 2018 at 10:49 am
Hi, I’m trying to lock down my PHP settings and wondered if I need url_fopen for EE4.x and Authorize.net allow_url_fopen Also, my current install doesn’t have the Authorize.net Accept Payment Gateway v1.0.1.p plugin but it is working. Do I need this as a new requirement for EE 4.x? TIA |
|
No, but it is required for the PDF’s to function.
Auth.net have deprecated AIM and SIM, see: https://developer.authorize.net/api/upgrade_guide/ They may at this present time, but will eventually stop so we recommend switching over to Auth.net Accept. |
|
Thanks! What PDF function? Do you mean the PDF receipts? |
|
Yes although it’s Receipts and Invoices. EE uses DOMPDF to generate the PDF’s on your site, DOMPDF requires allow_url_fopen to be enabled. |
|
Can PDF receipts be disabled and regular html/txt ones be sent instead? |
|
Neither are actually sent to the user, the user opens up the Invoice/Receipt and has a button at the top they can use to download the PDF version. You can disable the PDF versions if you want, but the user would need to open view the invoice/receipt and then uses the browsers print function to print it, which may not look all that great in the end. To disable the PDF’s go to Event Espresso -> Messages -> Settings. Click the PDF tab heading and then click the green toggle switch to disable them, the buttons will automatically be removed from the HTML version when you do this. |
|
Event Espresso -> Messages -> Settings Right? |
|
My apologies, that’s correct. I read the headers as I replied and had HTML on the brain, I’ll edit my post for any future readers. |
|
No problem, it happens. Thanks so much for your help! =) |
|
You’re most welcome 🙂 Any further questions just let us know. |
|
The support post ‘EE 4.x + Authorize.net – PHP Requirements’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.