Heeee’s Back 0

Well, that was fun.

The connectivity issue seems to have gone away on its own and you can’t troubleshoot something that’s not there. One of the truisms of troubleshooting is that intermittent problems are the hardest to track down.

It seems to have been what one tech I met in a previous incarnation called an “FM” problem. If he was at a customer site and the issue he was called to fix mysteriously went away and if the customer asked what it was, he would say, “Oh, that was an FM problem” and hastily make his escape (“FM” loosely translated means “freaking magic”).

The other problem I was dealing with had to do with the new version of WordPress. WP changed the default editor and, since I “upgraded” my WordPress late last Thursday, I have been unable to publish or revise posts. Clicking to publish or update resulted in a “Publishing (Updating) failed” error.

I found the solution at the WordPress support forums. The one I selected was to install the “Classic Editor” plugin, which worked for me because it was quicker than calling my hosting provider to find out how to enable wp-json and I didn’t like that gol-darned newmangled editor anyway.

Now I’m going to run off to recuperate from being in Geek Purgatory for the weekend.

And another H/T to Shaun Mullen for his assistance in working this out.

Afterthought:

Other things I tried, for the troubleshooters out there, included trying multiple browsers; disabling plugins one at a time and trying to post (this excellent suggestion came from a support rep at my hosting provider, as several of the plugins I use have to do with editing; it didn’t fix the problem, but it was still an excellent suggestion, as troubleshooting consists of ruling things out to narrow the list of suspects); and changing to one of the default themes provided by WordPress.