It has been a while, and this poor blog was not so much neglected as it became broken, as did a rush of other web services, all of them caused by ill-effects of well-intended upgrades. It was amazing, really, the damage that could be caused by something like an added mimetype mapping, totally stymied all support channels, similarly an old java app vs a remote API silently switched to HTTPS (Java8 does not follow redirects). And then however it happened when Debian decides to upgrade only command-line php8.3 to 8.4 and excessively weird things happen.
And those all now back in action, my attention returns here, having forgotten nearly everything I did learn about \(\LaTeX\) math and Lilypond support (I have notes, no worries) although I can report an answer to the puzzle of the previous posts, the extraneous paragraph tags WordPress likes to insert, I’m not sure who suggested it, but all it took was tagging the following to the end of wp-content/themes/twentysixteen/functions.php
// Prevent WP from adding <p> tags on all post types
function disable_wp_auto_p( $content ) {
remove_filter( 'the_content', 'wpautop' );
remove_filter( 'the_excerpt', 'wpautop' );
return $content;
}
add_filter( 'the_content', 'disable_wp_auto_p', 0 );
So thank you to whom ever it was that hipped me to that trick. It fixes blank spaces and also fixes the annoying footnote issue. Yay, three cheers for the Fediverse!
Back to the posting problem, I’d long since forgotten what the block was but drafting this post was a clear reminder: while the error says the backend is undefined, what it means is the elpa version of the ox-wp.el is broken, or I broke it somehow, and while there is a function in the kit to regenerate this file, don’t do it! I’m sure there is a trick, however a better trick turned out to be fetching the version from the git repo.
And here we are.