|
Form & Function
|
April 6, 2015 at 6:45 am
Hi
Having an issue with the transaction page ‘apply payment’ pop-up getting stuck in ‘processing’. We contacted our hosting provider who said that ‘the plugin is using url_fopen, which is an insecure PHP function that we have disabled at Synthesis by default and cannot re-enable.’.
We asked if it was possible to enable it on our site for the duration of the event and response was:
‘As for the fopen issue, as this is a big security risk, we cannot enable it under any circumstances. We do support CURL as an alternative to url_fopen, so you might want to let the developer know.’
The issue doesn’t appear on our dev site which uses a different hosting provider but we can’t change servers as mid-way through the event booking time and can’t afford any downtime. If there is a ‘big security risk’ in the code please advise if there is an update available or workaround as this issue is urgent and need the functionality at the bakend working asap.
Many thanks
Laura
|
|
Tony
|
April 6, 2015 at 7:11 am
Hi Laura,
fopen() is used mainly by the DOMPDF library that Event Espresso uses to create the PDF’s and also when writing to the EE Log files, this should not effect that pop-up.
Which version number of Event Espresso 4 are you using?
Do you have WP_DEBUG and/or error_reporting enabled on the site?
Can you check the server error logs and see if any error are being thrown when you try to use the Apply Payment popup?
|
|
Form & Function
|
April 6, 2015 at 8:15 am
Hi Tony
Thanks fr the quick response. We’re using EE Version 4.6.18.p
Nothing was showing in debug when trying to use the ‘Apply Payment’ pop up.
Server logs are showing EE errors as follows – have asked hosting provider if just a memory issue:
4/6/2015 12:54:08 PM – www: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 74 bytes) in /var/www/ifsweurope2015.org/wp-content/plugins/event-espresso-core-reg/core/db_models/fields/EE_Simple_HTML_Field.php on line 19
4/6/2015 12:08:51 PM – www: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 122880 bytes) in /var/www/ifsweurope2015.org/wp-content/plugins/event-espresso-core-reg/caffeinated/payment_methods/Aim/EEG_Aim.gateway.php on line 162
4/6/2015 11:28:47 AM – www: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 89 bytes) in /var/www/ifsweurope2015.org/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php on line 457
Cheers
Laura
|
|
Tony
|
April 6, 2015 at 8:31 am
Hi Laura,
Your site is running out of memory:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted
Means the site has tried to use more memory than than has been allocated.
134217728 bytes = 138MB which is rather high, but depends on how many plugins you are using and the types of plugins in use. For example Visual Composer is rather resource heavy if you are using that, Event Espresso can also be depending on the amount of Events/Registrations.
To fix this you’ll need to edit your wp-config.php file, add something like:
define( 'WP_MAX_MEMORY_LIMIT', '256M' );
which will increase the memory limit (if your host allows) you can find more info on this here:
https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
You may find a line similar to that already within that file, if so just increase the number to 256M rather than adding a new line.
Once you have done that does the apply payment work as expected?
|
|
Form & Function
|
April 7, 2015 at 5:34 am
Hi Tony
Thanks for your further advice, the site is rather plugin heavy but all pretty necessary – bizarrely the apply payment button is now working as expected after disabling BackupBuddy!
Thanks for your help, glad the issue is resolved 🙂
Cheers
Laura
|
|
Tony
|
April 7, 2015 at 6:34 am
The more plugins active, the more memory the site will use (it does depend heavily on the specific plugins in use) so disabling BackupBuddy has reduces the amount of memory the site is using which will allow EE to use that memory.
It does sound like you are close to the sites memory limit and will very likely run into this issue again somewhere so I would recommend you up the memory available to that site, you may need to contact your host (depending on how much memory they have allocated to you) and have them do this.
However I am glad its now working for you 🙂
I’ll mark this thread resolved.
|
