Moderator
t-p
(@t-p)
What did you do before this issue occurred? Update/install plugins? Update/install theme? update WP? Moved site? Anything else?
Thanks for the quick response @t-p.
I’m fairly sure update(s) of the theme or plugins were the last things that occurred. I can’t be too specific though, because one of the plugins is Automatic Plugin Updates, so any minor updates occur unattended.
Some progress…
Using cPanel, I uploaded a fresh copy of the wp-includes directory as a zip file, deleted the old directory, and replaced it with the new (expanded) wp-includes directory. Afterward, the editor showed the page in black text <yeah!>, and showed both the Visual and Text tabs – but the editor is stuck in Text mode.
I did the diagnostic dance again, de-activating all the plugins, activating Twenty Seventeen, and manually clearing the browser cache, but the editor remained stuck in Text mode.
The hunt continues…
I don’t know how to interpret the following output – hopefully it will make sense to others.
After de-activating all the plugins and activating Twenty Seventeen, I loaded a page in the editor at http://www.site-solutions.com and hit F12. The Inspector showed me a log file which I zipped as a txt file and left it at https://www.dropbox.com/s/uq51jlecsptr1ya/Error_log.zip?dl=0
Any clues?
Dennis
Moderator
t-p
(@t-p)
Troubleshooting with your browser: Your browser can help you identify JavaScript issues or conflicts and this article can assist you in doing that diagnosis. This could help identify Visual Editor issues as well.
Apologies for the late response @t-p. Life got in the way.
I visited the article you suggested. Here are the results, but the numbers:
1 – The error persisted in Chrome, Firefox, Internet Explorer, and Opera. Interestingly, the editor loaded in Chrome, Firefox, and Opera and showed the row of text buttons (b, i, link, b-quote, etc), while in Internet Explorer those buttons did not appear.
2 – The error persisted after adding define('SCRIPT_DEBUG', true);
just before Happy Blogging
.
3 – The console in Chrome contained the following (after I reloaded the page):
/wp-admin/post.php?post=114&action=edit:277 GET https://www.site-solutions.com/wp-content/plugins/google-analytics-for-wordpress/assets/css/images/menu-icon@2x.png 0 ()
inject.preload.js:373 GET blob:https://www.site-solutions.com/bc0eaad7-84ae-4777-bb34-889ebbc30acc 0 ()
(anonymous) @ inject.preload.js:373
__webpack_require__ @ bootstrap a58e717ca664391e8660:19
splitSelector.splitSelector @ common.js:103
__webpack_require__ @ bootstrap a58e717ca664391e8660:19
exports.textToRegExp @ bootstrap a58e717ca664391e8660:62
(anonymous) @ bootstrap a58e717ca664391e8660:62
load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.6:9 JQMIGRATE: Migrate is installed, version 1.4.1
nested.js?ver=ba049b38af3bdfb2c1538cef599fdd79:28 Uncaught TypeError: Cannot read property 'nodeName' of null
at klass.initialize (nested.js?ver=ba049b38af3bdfb2c1538cef599fdd79:28)
at new klass (nest-mootools.v1.11.js?ver=ba049b38af3bdfb2c1538cef599fdd79:361)
at pagemash.js?ver=ba049b38af3bdfb2c1538cef599fdd79:84
at returns (nest-mootools.v1.11.js?ver=ba049b38af3bdfb2c1538cef599fdd79:1424)
at nest-mootools.v1.11.js?ver=ba049b38af3bdfb2c1538cef599fdd79:1429
at nest-mootools.v1.11.js?ver=ba049b38af3bdfb2c1538cef599fdd79:2899
at Array.forEach (<anonymous>)
at fireEvent (nest-mootools.v1.11.js?ver=ba049b38af3bdfb2c1538cef599fdd79:2898)
at nest-mootools.v1.11.js?ver=ba049b38af3bdfb2c1538cef599fdd79:3605
at Function.<anonymous> (nest-mootools.v1.11.js?ver=ba049b38af3bdfb2c1538cef599fdd79:3609)
… I have no idea what the console’s told me, however.
Dennis
Moderator
t-p
(@t-p)
Try disabling google-analytics-for-wordpress
plugin.
I disabled the plugin and pulled the editor back up again – no change.
… for my next trick?
Dennis
Moderator
t-p
(@t-p)
To rule out any other plugin conflict, or a theme conflict,
Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.
If you can install plugins, install “Health Check”: https://wordpress.org/plugins/health-check/ On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.
Great plugin @t-p – thanks for the suggestion.
Sadly, nothing changed. I have “Text” buttons available at the top of the editor, and HTML showing in the editor.
Any other tricks up your sleeve?
Dennis