...among other innocuous tags like bold, blockquote, and so forth.
This patch implements Daniel P. Barron's simple fix. Also included is a revision of the trilema-specific database interaction in wp-comments-post.php to the default wp_comments table as pointed out by diana_coman.
*Edit March 26th 2019: My first regrind was still fucked up, as Daniel P. Barron graciously pointed out yet again. I've reground again using correct syntax. So then:
The secondly-reground patch:
mp-wp_html-comments-regrind.vpatch
The corresponding sig:
mp-wp_html-comments-regrind.vpatch.hanbot.sig
---fuxed files, for posterior---
*Edit March 25th 2019: I've reground this patch based on Daniel P. Barron's catch of my incorrect use of a default rather than a variable table name. The reground versions are:
Reground patch:
mp-wp_html-comments-fixed.vpatch
Reground sig:
mp-wp_html-comments-fixed.vpatch.hanbot.sig
The old patch:
mp-wp_html-comments-enabled.vpatch
My old sig:
mp-wp_html-comments-enabled.vpatch.hanbot.sig
Grab my pubkey, if needed, on the about page, or send !!key hanbot
to deedbot on Freenode IRC, while ye may.
Your "wp_comments" is something that you personally chose when you installed your mp-wp. I happen to have chosen something different, and therefor this patch would break my installation. Diana had suggested that you use the variable "$wpdb->comments" instead, which would work no matter what name was chosen for the database table.
Thank you for catching this. Reground.
You closed the first part of the string and then didn't concatenate the variable. This is invalid php that will result in a fatal error. It should look something like the following.
[...] first published and announced in #trilema last week but has since been reground to fit on top of hanbot's latest. Overall this patch proved to be an effective first step in mp-wp's healthy new lifestyle, [...]
[...] mp-wp_html-comments-regrind.vpatch (hanbot) (sauce) [...]