|
themakeden
|
September 30, 2013 at 7:40 pm
We recently had to switch hosting providers (we are now using bluehost), and had a few initial glitches with plugin permissions during the move that I was told were solved. However, although EE seems to be functioning more or less as normal, there are a number of error messages peppering various aspects of the registration process and the back end.
I’ve had to ignore this issue for a few weeks while I was on holiday, but now I am determined to resolve it. I decided to update my EE and wordpress before getting in touch, and encountered a number of additional error messages along the way.
They are too numerous to explain in this post, so I’ve tried to outline them (with screenshots) here: http://imgur.com/a/EwECn
Please let me know if you have any additional questions or thoughts as to what might be causing these types of error messages. We are happy to purchase premium support if need be.
|
|
Josh
|
October 1, 2013 at 9:55 am
Hi there,
It looks you need to contact your host and ask them to disable error display. That will fix most of the notices you are seeing. It may also be a case where the wp-config.php file has WP_DEBUG set to true.
The other thing you can do is edit your wp-config.php file and on the line after it sets WP_DEBUG add this:
@ini_set( 'display_errors', 'Off' );
If you have the Espresso JSON API plugin installed you will need to deactivate and delete the version you have installed now and download and install the new one. After you install the JSON API plugin please request a key reset from your account page (but please do not pay for the reset) and we will reset your key for free.
|
|
themakeden
|
October 1, 2013 at 8:46 pm
Thanks so much Josh!
So, we shouldn’t be concerned about the content of these error messages, assuming everything “seems” to be functioning properly?
I went in to wp-config and set WP_DEBUG was indeed set to “true”. I set it to “false” (instead of adding your suggested code) and it looks like the error messages are gone!
Let me know if there’s anything else I’m missing, but I’m glad this was an easy fix!
|
|
Dean
|
October 1, 2013 at 11:53 pm
Hi,
It is definitely best that WP_DEBUG is turned off and looking at those errors they are just notices advising that a variable hasn’t been set, they are not problematic. I’ll mark this as resolved.
|
