Default Post Category behavior changed after 4.3.1 upgrade
-
Backstory: I use Social and Twitter Tools to pull in my tweets and post them as normal posts. I format them differently than normal posts, and I’ve inserted PHP code to identify them. I’ve also hidden them from my monthly archives page.
So when my front page started to look wonky and my archives page blew up (i.e. began displaying all posts including tweets), I knew something was amiss.
I dug into the database and discovered that my “status” category had changed IDs. That would explain the archives page debacle. Located the new ID, plugged it into the PHP query filter, and all was well.
But.
Even though my default post category is set to “status” on the Writing Settings screen, my tweets were coming up with no category. When I changed the default category away from “status” and to something else, my tweets started coming in as a completely different category than the one I had chosen (“reviews” instead of “snippets”).
I’m going back in my brain, though, and recalling that when I write an actual post (rather than a tweet automatically being pulled in), and I forget to choose a category, it does post in the “reviews” category. So, I guess that’s been my default category all along? (Chalk that one up to Not Enough Of An Annoyance For Me To Have Done Anything About It.)
In any case, the default category selector doesn’t do anything. I’ve left a couple of the tweets in question in the category that they posted in, to show the issue.
Maybe this is also a Twitter Tools plug-in issue? But if it is, I think it’s secondary to the main problem of my default post category.
- The topic ‘Default Post Category behavior changed after 4.3.1 upgrade’ is closed to new replies.