WordPress update

I thought it only fair that I should add quick addendum to my previous missive on the difficulties of turning out blog content using WordPress 5.5 (the latest update at the time of writing) – should one be wedded (as am I) to the ‘Classic’ editor rather than whatever it is that WordPress want us to adopt now.

My complaint (should you have missed that message) was that the ‘Classic’ editor (which WordPress is trying to phase out) ceased to work after the recent upgrade to WordPress 5.5.

After further research online I have ascertained that the problem actually lies elsewhere – probably with one or more third party plugins that get referenced by the editor.

OK – now this is going to get a tiny bit technical, but I promise to keep it as simple as possible.

These older plugins had continued to work across previous upgrades because the WordPress build itself used to include a library called Jquery.Migrate – the purpose of which was to provide a mechanism for out of date code to continue to operate even if using deprecated methods. WordPress have now removed that library – hence the pain.

Some good-hearted folk from the Open-Source community have kindly and generously provided a workaround in the shape of a new plugin – Jquery.Migrate.Helper. This gets tools such a the Classic Editor working again – albeit with a constant background cacophony of warning messages.

WordPress seems to be determined to be shot of the whole affair, however, which doesn’t bode well for future upgrades… regardless of the veritable howls of protest from around the community.

Now – what else does that remind you of?