|
Sandy Milkey
|
September 2, 2015 at 10:15 am
This is a site that was working wonderfully this week with EE4, and as of yesterday afternoon we started getting this error.
I have read through many posts about this error in the forum and have tried multiple things.
At this time, I have completed deleted all cache plugins (was using Fastest Cache) and also requested the server admin to remove server level cache setting. I have made sure the cache folder is totally empty and looked for any weird files.
This started happening after a few things yesterday:
1) I upgraded EE4 to the latest stable version 4.8.7.p to address other bugs.
2) I made a back up of the website.
3) I enabled Fastest Cache plugin.
After this error began, I followed all the suggestions. I tested on 2 different computers on 2 different Internet networks.
I have a lot of custom registration fields and event description and data hard work put into this, so I really don’t want to disable EE4 or reinstall it. Hopefully someone can suggest something I missed!
On another note, I want to know if changing our domain name is going to require changes to our EE4 license. We are working on a staging domain right now and are getting ready to launch it to the live url this week.
|
|
Josh
|
September 2, 2015 at 11:23 am
Hi Sandy,
Have you checked the .htaccess file and the wp-config.php file to see if anything was left behind from the Fastest Cache plugin?
Regarding the license key on the production domain, when you go to change the domain name, you can go to your account page here and request a license key reset and we’ll reset the key.
A note on disabling Event Espresso: You can disable the Event Espresso plugin at any time and your registration fields and event data will be fine. All of the data and settings are stored on the server’s database, which we recommend making backups for, but when you deactivate Event Espresso the data stays put.
|
|
Sandy Milkey
|
September 2, 2015 at 3:22 pm
Hi Josh. Thanks for your feedback.
I have double checked the htaccess and wp-config files and looked through other directories just in case. Things look back to original format without any extra cache plugin code on the files. I asked a server admin for the hosting server to check also.
How long does resetting the license key usually take? I would like to know how this might impact the launching time and if there will be significant downtime for registration during that switch.
|
|
Josh
|
September 2, 2015 at 4:37 pm
There’s no downtime for the registration because the license key only affects the 1-click updates. The license key does not affect the registration process.
Can you restore the website from the backup that you made before installing the caching plugin?
|
|
Sandy Milkey
|
September 3, 2015 at 1:31 pm
This morning I restored the website from a back up that was before any cache plugin was installed and before upgrading to the latest version of EE4. It did bring back registration functionality, but other bugs were present because of the old EE4 version. We just upgraded EE4 to 4.8.7 WITHOUT installing any sort of caching feature. Now the error has returned!
So it appears to me this error is caused by the upgrade of Event Espresso and not the cache.
Any advice?
|
|
Josh
|
September 3, 2015 at 1:38 pm
Did you completely remove the old copy of the plugin before you uploaded the copy of the new version?
It might also help to know which version you updated from.
|
|
Sandy Milkey
|
September 3, 2015 at 1:47 pm
Hi Josh. No, I simply clicked the upgrade link option in the WP admin and then followed the buttons for Maintenance to migrate the database data to the new version. This was an upgrade from 4.7.6. Should I be doing the file upgrade by FTP only instead? Should I be doing this in steps?
|
|
Josh
|
September 3, 2015 at 2:48 pm
The one click update link will remove the old files before it uploads the new files, so that’s fine. Do you have a copy of the server’s PHP error logs that you can send to our email address? If so, please send a copy to support at eventespresso.com and we can investigate further.
|
