Could you add the following to your site’s wp-config.php file?
define('WP_DEBUG', true);
if ( WP_DEBUG ) {
@error_reporting( E_ALL );
@ini_set( 'log_errors', true );
@ini_set( 'log_errors_max_len', '0' );
define( 'WP_DEBUG_LOG', true );
define('WP_DEBUG_DISPLAY', false);
define( 'CONCATENATE_SCRIPTS', false );
define( 'SAVEQUERIES', true );
}
Once you’ve done so, try activating Jetpack again, and trigger the error. Then, check the wp-content/debug.log file for errors, and paste the results here. You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false); in the code above.
Thanks!
Hi, I confirmed earlier that this problem was still happening however I noted that it has something to do with when Akismet and Jetpack are activated at the same time. Akismet was updated 2 months ago and Jetpack was updated 1 week ago so I figured it was jetpack. As long as both are activated the problem persist. However, I am wondering if it’s a browser issue. I was using my windows 7 computer at work and IE 10. On my laptop I have Windows 10 and Chrome and now I can see the text in the editor. I will have to confirm this tomorrow. If it doesn’t show on the computer at work still then I’ll know it’s only that.
On another note. I tried the code above and I guess since it works on this browser, there was no debug error because no log was created.
Let me know what happens when you try from work, and if the debug log displays anything there!
Okay so it does happen at work. However, I don’t have access to my wp-config.php file from here. I’ll have to wait till I get home turn the debug back on and then come here do it and go back and check if it created the file. Thank you for your patience.
