|
Steve Amis
|
November 4, 2015 at 3:44 pm
I just activated event-espresso-core-reg and the site went down. Just white window with no content. I am using WP 4.3.1. I turned off all plugins except event-espresso-core-reg and the site still went down. Changed theme to Twenty-Fourteen and still won’t work. Is there something special I have to do to get this to work? EE3 was working when we used it earlier this year.
|
|
Garth
|
November 4, 2015 at 3:49 pm
Hi Steve,
How are you today?
A couple of things:
– What version of PHP are you using?
– Thanks for checking your theme…what other plugins do you have installed?
– Download the Requirements https://eventespresso.com/requirements/ plugin and that might give us some indication of any potential issues.
|
|
Steve Amis
|
November 4, 2015 at 4:04 pm
Not sure if this is the way to respond but your email was “noreply” PHP is 5.3.3. I’ll check the Espresso requirements and let you know. Thanks.
|
|
Steve Amis
|
November 4, 2015 at 4:23 pm
Tried to email and they came back. I checked the requirements and the only one we don’t meet is the PHP version. I’ve sent a note to the host to have them change it which they should since WordPress recommends it as well and they have many WordPress sites on their servers.
|
|
Lorenzo Orlando Caum
|
November 4, 2015 at 4:39 pm
Hi Steve, thanks for checking into that. In your original post, you mentioned that the page was completely blank.
Could you temporarily turn on WordPress debugging by adding the macro in the following link to your wp-config.php file?
https://gist.github.com/lorenzocaum/848801a1173be464fbe7#file-gistfile1-php
The wp-config.php file can be found in the WordPress root which is where the wp-admin, wp-content, and other files and folders for WordPress resides.
Then please try to trigger the error and you should see something on the screen. Could you copy and paste that here into a reply?
If you do not see an error on your screen, then please browse to this location using your SFTP or FTP client (e.g. FileZilla, Cyberduck):
/wp-content/debug.log
You should see an error recorded within the file. Please copy and paste that here in a reply as that will help us pinpoint exactly what is happen.
Then go ahead and deactivate WordPress debugging by removing the macro that was recently added or setting it to false and saving changes:
https://gist.github.com/lorenzocaum/848801a1173be464fbe7#gistcomment-1239850
Thanks!
—
Lorenzo
|
