|
corelearn
|
August 5, 2019 at 6:36 am
Hello! Over the weekend we upgraded the Event Espresso plugin to version 4.10.0.p on PHP 7.3. After doing the upgrade we were no longer able to us the WP admin panel. So, we rolled back to the previous plug-in version. Based on EE documentation, it looks like the plug-in is compatible with PHP 7.3. Do you know what step we may have missed to get the plug-in to work?
Thanks!
Emily
|
|
Tony
|
August 5, 2019 at 7:34 am
Hi Emily,
Was there an error being thrown at all? If so, do you have the error?
I run EE on multiple test sites using PHP 7.3 without any issues. When you say you couldn’t use the admin panel, do you mean the Dashboard? /wp-admin/?
If so, what did you see on the page? I’m guessing just a whitescreen?
|
|
corelearn
|
August 5, 2019 at 9:40 am
Hi Tony! No error was given. We just got the white screen.
Emily
|
|
Josh
|
August 5, 2019 at 10:21 am
Hi,
You could check the PHP error log (available from your host’s User Portal). The time when you had 4.10.0 activated will likely have a Fatal Error. Sometimes it happens where the download of the new version gets interrupted which results in some missing files, which would result in the blank admin screen you experienced.
In any case we’ll get a better picture of what happened and how to fix if you can look at the PHP error log.
|
|
corelearn
|
August 5, 2019 at 4:47 pm
Hello! We went through the steps again of upgrading the EE plug-in again, this time in our staging environment. Here’s what happened:
– It looks like the Event Espresso – Promotions (EE 4.9.10+) plugin update crashed the staging site.
– We looked through every logged event and nothing is showing the actual error causing the problem. The only events that came up are these and don’t seem to be related:
[05-Aug-2019 21:47:41 UTC] PHP Notice: Undefined variable: core in /nas/content/live/corelearnstage/wp-content/themes/core/options/sample/config1.php on line 67
[05-Aug-2019 21:47:41 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 117
[05-Aug-2019 21:47:41 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 118
– We were not able to do the PHP 7.3 upgrade because the EE promotions plugin crashes the site and the admin portal as well.
Any ideas?
Emily
|
|
Tony
|
August 6, 2019 at 3:54 am
Hi Emily,
Those notices are unrelated and are from the theme.
If the EE promotions plugin is crashing the site, there should be a log of the error. A white screen means a fatal error is being thrown and by default, your site will be setup to not display errors to the screen (which is correct) but it should be logging them.
As mentioned, I’m running Event Espresso with most of the add-ons on multiple sites using PHP7.3 without an issue which means we can’t troubleshoot this without the error being thrown.
On the staging site can you set WP_DEBUG to true and test again? The error should then be shown on the screen in place of just a white screen. To enable WP_DEBUG you edit the staging site’s wp-config.php file and change:
define( 'WP_DEBUG', false );
To be
define( 'WP_DEBUG', true );
|
|
corelearn
|
August 8, 2019 at 1:15 pm
Hello! Here are the results of the debug log after activating the Event Espresso plugins.
[05-Aug-2019 21:47:41 UTC] PHP Notice: Undefined variable: core in /nas/content/live/corelearnstage/wp-content/themes/core/options/sample/config1.php on line 67 [05-Aug-2019 21:47:41 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 117 [05-Aug-2019 21:47:41 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 118 [05-Aug-2019 21:55:04 UTC] PHP Notice: Undefined variable: core in /nas/content/live/corelearnstage/wp-content/themes/core/options/sample/config1.php on line 67 [05-Aug-2019 21:55:04 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 117 [05-Aug-2019 21:55:04 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 118 [05-Aug-2019 21:57:32 UTC] PHP Notice: Undefined variable: core in /nas/content/live/corelearnstage/wp-content/themes/core/options/sample/config1.php on line 67 [05-Aug-2019 21:57:32 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 117 [05-Aug-2019 21:57:32 UTC] PHP Notice: Undefined index: HTTP_HOST in /nas/content/live/corelearnstage/wp-content/themes/core/options/metaboxes/extensions/metaboxes/extension_metaboxes.php on line 118 [08-Aug-2019 15:25:30 UTC] PHP Notice: Undefined index: SERVER_NAME in /nas/content/live/corelearnstage/wp-includes/pluggable.php on line 333
Please let me know if this gives you any insight into what may be going on.
Thanks!
|
|
corelearn
|
August 8, 2019 at 1:20 pm
Hello! I just wanted to confirm that you received the debug log. I submitted it but got an error. When I tried to resubmit, I got an error that it was a duplicate post.
Thanks!
Emily
|
|
Tony
|
August 8, 2019 at 1:33 pm
Hi Emily,
The post had been flagged as spam, likely due to the content, so I’ve removed that flag.
Those notices are all from your theme and wouldn’t usually cause a whitescreen.
Is EE4 currently installed on your staging server? If so I can take a look if you prefer? If so you can send the details requested here:
https://eventespresso.com/send-login-details/
FTP credentials are required for this as I’ll need to enable Debug mode.
Note – generally we require a support token to work directly on a site, however, I want to get hold of the error first and confirm what the issue is. If I get the error to display and it turns out to be a theme/plugin conflict we would require a support token to investigate further.
|
|
Josh
|
August 8, 2019 at 1:35 pm
Hi Emily,
I’m afraid all the PHP notices you posted here are showing issues from the theme, nothing there mentions a fatal error or any type of error from the Promotions add-on.
Instead of trying to find the error in a log, you can make it so the error just prints to the screen, instead of just a white screen.
If you go to edit your staging site’s wp-config.php file, you’ll make sure it says this:
define( 'WP_DEBUG', true );
and this:
define( 'WP_DEBUG_DISPLAY', true );
Then, you go to the page or activate the plugin that caused the white screen. Instead of only a white screen, you’ll also see an error message.
|
