What makes the plugin useful is that it allows you to turn postings into different, well, kinds of posts. Such as a reply, or a check-in, rsvp, bookmark or favourite. It adds the right microformats so that computers can semantically analyse a post’s purpose, and adds the styling to display them.
My main issue with it was that it places key elements such as the weblink you’re responding to outside the posting itself. It gets stored in the database as belonging to the PostKinds plugin. Meaning if you ever switch it off, that gets wiped from your posting (although it’s still in the database then). This was a dependency I needed to get rid of.
For new postings from summer 2021 I did that by deploying small templates that allow me to mark a posting as reply, rsvp, favourite, bookmark, or check-in, within the postings I’m writing.
I used the PostKinds plugin heavily for 3 years, and most heavily in 2019. That legacy from 2018-2021 was still there, requiring the PostKinds plugin to remain enabled. Until today. Over time I had slowly changed posts when I encountered them, and in the past week I did the remainder.
Another issue is that PostKinds only works in the classic WordPress editor, and not in the now default Gutenberg editor. At some point that would hinder the ability to upgrade WordPress.
Solong PostKinds, thanks for all the fish!
I wish you’d said something. I have considered writing a migration tool to render the properties and save them in content if someone wanted to disable it, but being as I wasn’t leaving, it wasn’t a priority for me, but would have given it a quick shot if someone needed it. I hate to think people feel locked in.
Beyond that, not supporting the block editor is a choice, I know. Have some long term compromise thoughts on that, but…nothing has moved much.
Hi David, I just came across your comment and I’m in exactly the same situation. Is there a migration tool now?
Thanks.