Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
I enabled the debugger within the wpconfig.php file and enabled the error console via chrome.
There were no errors on the console…only the following statement:
JQMIGRATE: Migrate is installed with logging active, version 1.4.1.
I cleared the cache and reloaded the page…no change.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Can you show us an example page that contains the issue? I don’t mean in the dashboard. Thanks.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Hmm unfortunately (for debugging purposes) your webpages look fine on the front-end.
When you said you disabled all plugins and switched to the default theme, did you switch to the default theme with all plugins deactivated still? Or did you deactivate all plugins, re-enable them and then switch?
I have deactivated all plugins and have switched to the default theme at the same time.
Hey — I just wanted to chime in because I had the exact same problem. I tried everything that you tried, but I still had a blank visual editor with a word count of 0. Also, all commas and quotation marks in all posts were replaced with a question mark in a black diamond.
I just found a way to fix the problem, with a small change to the ‘db.php’ file that is located in the ‘wp-content’ folder. I opened that file up in a text editor, and noticed that the first function starts like this:
function set_charset( $dbh, $charset = null, $collate = null )
I changed the charset from ‘null’ to ‘utf8’, like this:
function set_charset( $dbh, $charset = ‘utf8’, $collate = null )
That change fixed both of my problems. Not sure if it would work for you, but thought I’d share just in case. This issue seems to have all sorts of remedies…not all of which work for everyone.
Shanse2, thank you so much. I think that you identified the root cause of the issue.
I didn’t have a db.php file in the wp-content directory. Instead, I added:
define(‘DB_CHARSET’, ‘utf8’);
define(‘DB_COLLATE’, ”);
to the wp-config.php file and the blank text edit box with the 0 word count AND the question mark in the black diamond problems went away from all of my posts.
My database/website was created many years ago, so my questions are:
1. How do I tell what charset the database is?
2. If it is the old Latin1 charset, do I need to change the database to UTF8?
3. Are there any problems with specifying the charset in the wp-config file without changing the underlying database charset?
Thoughts from the experts out there?
Nice, I’m glad that worked for you. Interestingly enough, I tried changing those lines in my files, and it didn’t work.
I wish I could answer your questions, but I don’t know enough about php or databases. I’ve asked one of the tech guys here in my office to come look at the fix I made and tell me if it’s the right thing to do. I’ll see if he knows about identifying/changing the database charset.
Thanks – let me know what he says
