Tested Omments After Unborking Them

Comments were borked:

• Primarily because when the [family blogging] Tagify module is disabled for flakiness, it then disables the fields for which had been providing an autocomplete widget, instead of offering the option of selecting a well-proven substitute widget (say, the previous default).1
• And because the out-of-the-box comment block formatting needed to be aligned with the rest of the site.
• And finally because in the course of this initial prettification I had set some fields to display: none in CSS that turned out to be load-bearing.

So I unborked the fields that Tagify borked, unborked the CSS that I had borked, and did some polishing.

Now to test:

1. ☑ Do comments properly nest?
2. ☑ Are they prettily styled?
3. ☑ Does comment moderation still work?

NOTES

1 If you have a site with a complex content types that have a lot of fields, that’s a total PITA, because you need to put your fields back in order.

Not only that: In the course of this butchery, Tagify also disassociates fields with entity references from their handlers, so if your field references tags, you, the harried administrator, need to resubmit the settings for the field in “Manage Fields” to get the handler back. For every single content type. Manually. And don’t tell me to go in the database or write some PHP.

So if you disable Tagify, you not only mess up your field structure, you mess up every field that uses tags or references views. It shouldn’t be this hard. Who coded Tagify? DOGE?

On the bright side, no data is lost, which is a mercy.