|
rccompetes
|
April 4, 2017 at 7:11 pm
We have been running the Event Espresso plugin(s) on our WordPress Site running the Avada WP Theme. Everything was working great and now the Event Espresso Plugin’s are breaking our Theme and Site. The site works and looks great until we attempt to activate the Event Espresso Plugin(s). When we attempt to activate the site breaks and we can no longer login to our WP Dashboard, we then have to go back and disable ALL plugins to once again gain access. Not sure what happened since we haven’t made any site changes since it was working flawlessly. The only changes would have been Theme and Plugin Updates. Please advise ASAP.
|
|
Tony
|
April 5, 2017 at 3:01 am
Hi there,
When we attempt to activate the site breaks and we can no longer login to our WP Dashboard
What happens when you log in? I’m guessing just a whitescreen?
If so there is likely a fatal error being thrown but it could be from anything, usually its caused by the server running our of memory but there are many different causes.
Do you have access to the server error logs? Take a look in there and look for any fatal errors in the logs.
we then have to go back and disable ALL plugins to once again gain access.
If its only happening when EE is activated you don’t need to de-activate all plugins, just rename the event-espresso-core-reg directory within plugins and refresh the admin, that will disable just EE.
Not sure what happened since we haven’t made any site changes since it was working flawlessly. The only changes would have been Theme and Plugin Updates.
We need the error that is being thrown when EE is active but it could be a conflict with the theme or a plugin now their code has been updated but again we’ll need the full error message to narrow this down more.
If you don’t have access to the error logs you’ll need to enable WP_DEBUG on the site, then activate EE and see what error message shows on the page.
If you post that here we can investigate further.
|
|
rccompetes
|
April 14, 2017 at 1:21 pm
When trying to access the site we are receiving one or more messages.
Internal Server Error
502 Bad Gateway and or
503 Service Unavailable, the server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
GoDaddy Support has manually updated the EE core plugin to the current version, and the issue was resolved for a short time, however when attempting to login to the dashboard the issues began happening again.
Is this an issue where I can purchase a support token and have you fix the problem? What do you suggest?
Thanks!
|
|
Josh
|
April 14, 2017 at 1:28 pm
This sounds like an issue with the hosting environment, which is something that we don’t have access to. Does the Godaddy support tech have a clue why the site was working fine before it stopped working suddenly? Usually this sort of thing happens when there’s a change to the hosting configuration.
|
|
rccompetes
|
April 16, 2017 at 6:31 pm
Josh,
Below is the information we received from GoDaddy the site is hosted on there “managed WordPress” platform. Can you review and advise ASAP. Thanks!
GODADDY RESPONSE BELOW
We have deactivated the Wordfence plugin. We suspect that this is a cached response. Just to confirm, are you using CDN for your site? If yes, we suggest clearing or disabling it. After disabling the plugin, however, we noticed that the issue still persists. We went ahead and turned on the Debug feature of WordPress and found the following errors:
20:19:40\”;i:566;s:19:\”2017-04-16 20:19:44\”;i:567;s:19:\”2017-04-16 20:47:56\”;}}’ WHERE option_name = ‘espresso_db_update’ made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, EE_Bootstrap::detect_activations_or_upgrades, do_action(‘AHEE__EE_Bootstrap__detect_activations_or_upgrades’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, EE_System->detect_activations_or_upgrades, EE_System->detect_if_activation_or_upgrade, EE_System->_handle_core_version_change, EE_System->update_list_of_installed_versions, update_option
[16-Apr-2017 20:47:57 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/content/a2pnexwpnas01_data02/40/3491240/html/wp-includes/wp-db.php:1405) in /home/content/a2pnexwpnas01_data02/40/3491240/html/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php on line 107
[16-Apr-2017 20:47:57 UTC] PHP Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/content/a2pnexwpnas01_data02/40/3491240/html/wp-includes/wp-db.php:1405) in /home/content/a2pnexwpnas01_data02/40/3491240/html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 463.
If you would, please contact your plugin developer and send the debug errors to them for diagnosis.
You can send their reply to us via this email and we would be happy to implement the fix they would like to apply.
A backup of your website was completed before performing this request.
|
|
Josh
|
April 17, 2017 at 9:23 am
Hi there,
The errors they shared with you are not actually caused by Event Espresso, those are symptoms of another problem. Are you running any plugins that cache the database?
|
|
rccompetes
|
April 21, 2017 at 11:13 am
Josh,
Finally got things resolved. We ended up moving to a Linux cPanel environment for hosting and disabled all caching. Thanks for pointing us in the right direction.
One last question for now… We are running the current version of WordPress 4.7.4 and have a EE plugin that needs to be updated.
Event Espresso – MER – Multi Event Registration (EE 4.7.0+)
You have version 2.0.11.p installed. Update to 2.0.12.p. View version 2.0.12.p details. Compatibility with WordPress 4.7.4: Unknown
Is this compatible with WordPress 4.7.4?
Please advise.
Jeff
|
|
Josh
|
April 21, 2017 at 11:45 am
Hi Jeff,
Yes the Multi Event Registration plugin (version 2.0.12.p) was tested to verify compatibility with WordPress 4.7.4.
|
