|
Miriam Kuta
|
May 19, 2017 at 10:04 pm
I recently updated my Event Espresso EE4 core plugin and now I can not access my WordPress admin dashboard unless I manually disable the plugin. I’ve tried reinstalling the core-reg files from the zip archive to no avail. The calendar plugin and SIM gateway plugins are up-to-date, but are not causing any problems. Would you be able to suggest anything? I can send my WordPress login information if you wish to login to the site, I would need to disable the plugin first though.
|
|
Tony
|
May 22, 2017 at 4:31 am
Hi Miriam,
What happens when you log in with Event Espresso active? Whitescreen?
Have you checked the server’s error logs to see if there are any errors being thrown when you try to log in? You may need to enabled WP_DEBUG and log in with EE active to see any errors that are being thrown.
If you see any errors can you post those here so we can investigate further?
|
|
Miriam Kuta
|
May 23, 2017 at 7:40 am
Hello Tony,
When I login to WordPress with the Event Espresso plugin active, all I get is a whitescreen. I turned on debugging in the wp-config file, but no errors are being thrown on the blank page. Once I turn the plugin off, everything with WordPress is fine. After looking in the server logs, I did find an error that seems to keep reoccurring. I’ve included the error below:
line 236
PHP Deprecated: Function mcrypt_create_iv() is deprecated in /hermes/bosnaweb03b/b2504/ipg.thechilledpalettecom/calendar/wp-content/plugins/event-espresso-core-reg/core/EE_Encryption.core.php on line 238
PHP Deprecated: Function mcrypt_encrypt() is deprecated in /hermes/bosnaweb03b/b2504/ipg.thechilled
|
|
Josh
|
May 23, 2017 at 7:46 am
Hi Miriam,
If you can complete the form on this secure page, Event Espresso support staff can investigate further.
|
|
Josh
|
May 23, 2017 at 9:21 am
Hi again,
We receieved the information you sent. I’m afraid the WordPress username you sent isn’t valid. Can you resend the form with the correct information? The FTP info you sent was actually correct so no need to resend that part.
|
|
Miriam Kuta
|
May 23, 2017 at 9:23 am
user name – *redacted*
-
This reply was modified 7 years, 4 months ago by
 Josh. Reason: removed username
|
|
Josh
|
May 23, 2017 at 9:36 am
Thank you, but please don’t post information like this in the forums. Also, the password you sent with the form is invalid. Please resend the form and we’ll take a look at the problem on your site.
|
|
Josh
|
May 23, 2017 at 9:58 am
You can try logging in now and we’ll wait until you send the correct password. Then two you sent in so far were not valid.
|
|
Josh
|
May 23, 2017 at 10:43 am
It looks like there’s an issue with the .htaccess files on your server. There’s one located at the root level and one in the /calendar directory.
Even with Event Espresso deactivated if you go to the WP > Settings > Permalinks page and try to save, it logs you out and then it tries to redirect you from the login screen to the Permalinks page, which then results in a redirect loop. My guess is the .htaccess file in the root level needs to be cleaned up. Once that’s done you’ll be able to reactivate Event Espresso.
|
|
Miriam Kuta
|
May 24, 2017 at 10:05 am
Hello Josh,
I took a look at the .htaccess file in the root level and didn’t see anything out of the ordinary. I compared it to a site backup before the EE4 update and nothing had changed in the file. I even removed the root level htaccess file and reenabled the EE4 plugin, but was still getting server errors when trying to log out. I disabled Event Espresso again in order to regain access to the site again.
One thing to note is that when I had Event Espresso deactivated, I was able to go to the WP Permalinks page and successfully save. I never got the redirect loop that you described. I got the “Permalink structure updated.” message once saving.
Any other suggestions?
|
|
Josh
|
May 24, 2017 at 11:11 am
I even removed the root level htaccess file and reenabled the EE4 plugin, but was still getting server errors when trying to log out.
Are the server errors getting logged somewhere?
|
|
Miriam Kuta
|
May 24, 2017 at 11:54 am
the error log is located at \stats\cgi_error_log
|
|
Josh
|
May 24, 2017 at 12:41 pm
That particular error log isn’t logging any errors from when the wp-login.php page fails to load.
|
|
Miriam Kuta
|
May 24, 2017 at 2:57 pm
That’s the only error log that the website has
|
|
Josh
|
May 24, 2017 at 4:49 pm
Yes and it wasn’t really helpful. I think I found the problem and it was related to the cron option stored in the _options table. I cleared the option and your wp-login.php page is working now.
|
