|
afqam_webmaster
|
April 26, 2019 at 1:18 pm
This same issue happened a few weeks ago — while our site was still running php5.6 That time, the error cleared up after we deactivated EE. Our hosting company did also advise us to update to php7.3 — which we did. EE seemed to be working fine until this morning, but now we’ve had trouble again which was also resolved by deactivating EE. Our host is SiteGround.
Today, afqam.org showed only php errors, and would not redirect (afqam.org should redirect to afqam.org/wp15). To the best of our knowledge:
We haven’t made any changes that could / should have caused this.
The server didn’t make any changes that could / should have caused this.
Here are the php errors from afqam.org – when it wouldn’t redirect:
Warning: array_merge(): Expected parameter 2 to be an array, null given in /xxx/xxx/xxx/xxx/wp-includes/load.php on line 66
Warning: session_start(): Cannot start session when headers already sent in /xxx/xxx/xxx/xxx/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65
Warning: Cannot modify header information – headers already sent by (output started at /xxx/xxx/xxx/xxx/wp-includes/load.php:66) in /xxx/xxx/xxx/xxx/wp-includes/pluggable.php on line 1251
Warning: Cannot modify header information – headers already sent by (output started at /xxx/xxx/xxx/xxx/wp-includes/load.php:66) in /xxx/xxx/xxx/xxx/wp-includes/pluggable.php on line 1254
Advice or thoughts? Thank you.
|
|
Josh
|
April 26, 2019 at 3:08 pm
The PHP warnings seem to be caused by something other than Event Espresso 4.
The issue may be related to this:
https://mrwweb.com/solving-array_merge-argument-2-on-load-php-line-63-on-siteground/
I can also point you in the direction of the WordPress troubleshooting guide for “headers already sent”.
https://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F
|
