|
Dr. Shefali
|
May 29, 2018 at 10:09 am
For some reason, after installing the EE4 Events Calendar Addon, the EE4 stop working and now the admin dashboard cannot access anymore. We temporarily deactivated the EE4 plugin, please help we need to reactivate asap.
|
|
Tony
|
May 29, 2018 at 10:28 am
Hi there
A whitescreen means a fatal error is being thrown, we’ll need that error to know what the problem is.
If you look in the server’s error logs do you see any errors from EE?
|
|
Josh
|
May 29, 2018 at 11:06 am
Hi there,
You could probably reactivate the core Event Espresso plugin, but do not reactivate the Calendar add-on until we can investigate further.
|
|
Dr. Shefali
|
May 29, 2018 at 12:15 pm
it doesn’t work too, even I deleted the EE Calendar Addon, if I tried to reactivate the EE plugin, got white screen. please resolve asap.
|
|
Josh
|
May 29, 2018 at 12:34 pm
OK so adding the calendar add-on doesn’t seem to have caused this. Has anything else been added to the site around the time EE4 stopped working? If you deactivate all plugins and switch to one of the default themes does WordPress allow EE4 to activate?
|
|
Dr. Shefali
|
May 29, 2018 at 1:12 pm
Nothing, just the EE Calendar added nothing else.
|
|
Josh
|
May 29, 2018 at 1:18 pm
If you deactivate all plugins and switch to one of the default themes does WordPress allow EE4 to activate?
|
|
Dr. Shefali
|
May 29, 2018 at 3:59 pm
Still didn’t work.. we have an active event, and need to fix the registration page asap.. can you please troubleshoot?
|
|
Josh
|
May 29, 2018 at 4:12 pm
Can you complete this form? If you can complete the form we can troubleshoot.
|
|
Dr. Shefali
|
May 29, 2018 at 10:53 pm
Just filled out the form/
|
|
Tony
|
May 30, 2018 at 5:28 am
Hi there,
This is caused by an issue that we will need to fix in Event Espresso core so I have reverted the version installed on your site back to 4.9.61, the Calendar add-on is now activated…
However, as you had an older version of the calendar activated previuously EE needs to migrate the old data over to the new version, we recommend you create a backup of the database before doing this (just to be safe). Once you have a bckup of the database go to Event Espresso -> Maintenance and follow the instructions to migrate the data.
After that EE should work normally again.
Once the migration has been completed you can update EE to the latest version and it will work as expected, it’s the maintenance mode for the calendar settings that is causing the problem, once that has been done the latest version should work fine.
|
|
Dr. Shefali
|
May 30, 2018 at 8:36 am
Hello,
I did the instructions above and updated the EE, I got an error:
“Event Espresso Calendar could not be activated. Please ensure that Event Espresso version 4.3.0.p or higher is running”
And the EE deactivated again. I reactivated it but the Calendar stop working again. Can you please check? And remove the duplicate copy of EE?
|
|
Tony
|
May 30, 2018 at 9:09 am
It looks like you have activated the version of Event Espresso that was deactivated prior to the above, the version that was currently active on the site was the one that is sitting in the event-espresso-core-reg2 directory.
I’ve switched those back out and deleted the duplicate version (we don’t delete anything on the site without permission as I have no idea if you’ve customized anything, as you asked, I’ve removed it).
The calendar is now active, I’m not sure where it is in use on the site currently, can you link me to a page using the calendar?
|
|
Dr. Shefali
|
May 30, 2018 at 1:41 pm
Thanks Tony. We’re about to setup the calendar page when we installed it. So no page setup yet. Are all working now?
|
|
Tony
|
May 30, 2018 at 2:10 pm
I can’t see any issues with EE, your site did show 502 bad gateway a couple of times which is usually an issue with your host, running out of resources etc, if that continues I recommend contacting your host to have them investigate.
Other than that the site appears to be working as expected now.
|
|
Dr. Shefali
|
May 30, 2018 at 2:20 pm
Thank you for the help. I will mark this thread as resolved now.
Thanks again.
|
