|
manders
|
January 20, 2018 at 10:35 am
Hi
Last night we made update to EE 4.9.55 (previously 4.9.53), we also updated Jupiter theme. Everything else is good, except when someone tries to register, they get this error – and not able to proceed:
Warning: array_merge(): Argument #1 is not an array in /home/(ouraccount)/public_html/(folder)/wp-content/plugins/event-espresso-core-reg/core/EE_Error.core.php on line 783
Warning: Cannot modify header information – headers already sent by (output started at /home/(ouraccount)/public_html/(folder)/wp-content/plugins/event-espresso-core-reg/core/EE_Error.core.php:783) in /home/arworksh/public_html/milton/wp-includes/pluggable.php on line 1216
Please assist.
thanks
|
|
Josh
|
January 22, 2018 at 11:17 am
Hi there,
We can assist. Can you post a link to the event page where this is happening so we can investigate? Thank you.
|
|
manders
|
January 23, 2018 at 1:25 am
Hi
This is happening to all the events here: https://arworkshop.com/newtown/
only when someone tries to register.
Currently we enabled debug, to skip the error message and allow the script to proceed.
This is what we found in the log file:
[23-Jan-2018 03:24:35 UTC] PHP Warning: array_merge(): Argument #1 is not an array in /home/{username}/public_html/newtown/wp-content/plugins/event-espresso-core-reg/core/EE_Error.core.php on line 783
Thanks for your help.
|
|
Alan Lewis
|
January 23, 2018 at 2:24 am
I am having the same issue
|
|
Josh
|
January 23, 2018 at 7:12 am
@manders:
I’m not seeing any errors when I test a registration, are there some specific steps I need to follow to see the error?
@Alan:
We’re more than happy to help so please start a new topic and include some information about your site and how we can replicate the error.
|
|
manders
|
January 23, 2018 at 12:38 pm
We have a lot of classes (events) everyday and has enabled WP Debug so the error did not show and transactions can keep going on. But the error is still there, and recorded in the log file.
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
if ( WP_DEBUG ) {
@ini_set( 'display_errors', 0 );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
}
|
|
Josh
|
January 23, 2018 at 12:49 pm
Are there some specific steps I need to follow to see the error or are they only recorded into the log file? If the PHP warning is only being recorded into a log file and it’s not disrupting something, then you definitely need to keep WP_DEBUG set to false.
If the PHP warning is disrupting the checkout flow, even with WP_DEBUG set to false, please outline the steps to make that happen so we can investigate further.
|
|
manders
|
January 24, 2018 at 12:58 pm
Yes it disturbs the registration if WP_DEBUG set to false.
Steps:
1. Pick one of the available workshops
2. choose qty and click register
And it gives the error.
|
|
Josh
|
January 24, 2018 at 1:59 pm
Is there a specific browser I need to use to get it to show an error? The reason I ask is because I tested a registration on https://arworkshop.com/newtown/events/plank-wood-sign-lazy-susan-round-sign-or-centerpiece-box-workshop-17/
and I see no errors.
|
|
manders
|
January 24, 2018 at 3:21 pm
It happens to all browsers, right now the DEBUG is set to true, so all registrations can pass. We are trying to avoid loosing business.
Will you be available tomorrow morning? I will set DEBUG to false so you can test it, sometime 7 – 9 AM? thanks
|
|
Tony
|
January 25, 2018 at 5:29 am
With regards to WP_DEBUG, the error would normally display when WP_DEBUG is true and not display when WP_DEBUG is false.
The reason it’s not is the snippet in use on your site when WP_DEBUG is enabled tells the server not to display any errors:
//Set WP_DEBUG to true.
define( 'WP_DEBUG', true );
if ( WP_DEBUG ) {
//If WP_DEBUG is true set display_errors to false and
//tell WP to set your server to log the errors and NOT to display them.
@ini_set( 'display_errors', 0 );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
}
So what that means is your server is currently set to display_errors on the page and you don’t really want that on a production server, I’d recommend contacting your host and have them set PHP to not display the errors by default (log them by all means but don’t display them).
That way you set WP_DEBUG to true to display the errors when debugging the site and false any other time (that’s the expected use case for WP_Debug).
Now, having said all that, that doesn’t actually fix the error, it just stops your server from disrupting the registration process. I know you are doing that right now using WP_DEBUG, but that setup is the opposite of how its supposed to be.
To investigate the problem, I’d like to take a quick look at your site’s settings in the database, would that be ok? If so you can use this form to send temp login details:
https://eventespresso.com/send-login-details/
Note that to do so I’ll need to install a plugin on your site, we only install plugins if we have FTP credentials to the server so those are also required in this case.
|
|
manders
|
January 30, 2018 at 9:00 pm
Issue fixed by updating to latest version 4.9.56.p .
|
|
Tony
|
January 31, 2018 at 3:04 am
Thank you for the update, I’m glad it’s now working for you.
|
