WordPress might not be showing your Custom Post Types and Custom Taxonomies on the Menus screen for a really stupid reason

I’m working on a new WordPress site that’s going to have both custom post types and custom taxonomies, and I want my custom taxonomies’ archive pages to be in the site’s navigation menu.

Seems like it should be easy, right? If you set show_in_nav_menus to true in register_post_type() or register_taxonomy(), you’re supposed to get access to add them to your menus.

But when I set that, they still didn’t appear on the Menus screen. What the…?

I found it exceptionally difficult to track down any information about this, although I did eventually find a tutorial on the very subject but… whoa, those are some old screenshots! The tutorial is a decade old.

Nonetheless, I proceeded to try to make it work, with extensive customizations to suit my needs. Strangely — and it should have been a clue to me — they wouldn’t appear if I gave the meta boxes the name of my custom taxonomy, but if I gave them an arbitrary name, it did work. But there were still some quirks, so I started digging around in the inspector to figure out what was what. Then I discovered something really odd.

They were already in the page. Only, they weren’t displaying. That’s because they all had a CSS class hide-if-js applied. So what’s that all about?

Well… it was really stupid. They were “unchecked” under Screen Options. You know, that little tab at the top right of every WordPress admin page.

My best guess here is that it’s because I had already been to the Menus page for this site before I started building the CPTs and taxonomies, so when I added them to the theme, my personal preferences for Screen Options on the Menus page had already been set, and therefore they defaulted to “unchecked.”

That seems kind of stupid. More specifically, it seems stupid that WordPress gives you the option to turn the items in the Add menu items list off. But it definitely should default any new items that suddenly appear, i.e. that are not already “on” or “off” in your preferences, to “on.” So you, like, know they exist.

The Lorax: shockingly bad

I was not at all shocked that the new Lorax movie is bad. But I was shocked at how bad. Without question, Dr. Seuss has always been my favorite children’s author, ever since I filled the entire checkout card of my elementary school’s copy of The Cat in the Hat with my name. Yes, I just renewed it over and over, because I loved it. (And, apparently, my mom did not, or she’d have just broken down and bought me my own copy.)

Over the years I read a lot of Seuss books at the school library, but none made such an impression, both immediate and lasting, as The Lorax. I loved it like nothing else, and I still do. I loved the book, and I loved the 1972 animated TV special, which not only captured and expanded upon the spirit of the book, but did so with the kind of funky music that only could have appeared in a children’s television program in that decade.

Therefore, it was almost a given that I would hate the new CGI animated feature film adaptation. But I was not prepared for how much I would hate it. OK, the notorious Mazda commercial gave me a clue, but I had been lulled since first staring gape-jawed in disbelief at the audacity of a car company claiming that an SUV with a standard combustion engine was “Truffula tree approved” into thinking that maybe the movie wouldn’t be so bad, after all.

Oh, how wrong I was. I was wrong — as were the filmmakers — in so many ways that I can barely begin to catalog them.

Fortunately I don’t have to. In his Vulture review, The Badness of The Lorax Is a Shock, David Edelstein says it all for me.


We disagree over whether the source material is any good, apparently, and Edelstein seems to like most the part of the movie I hate most — the tacked on conventional family movie chase sequence in the final 20 minutes. I found it so gratuitous and unbearable (and frankly just plain boring) that I excused myself to go to the bathroom, but I really just wanted to get the hell out of the theater so I didn’t have to witness any further abomination.

Please. Do not see this movie. Read the book. Or watch the 1972 TV special four times instead.

“All in” is right

Today, according to banner ads and discussions from the likes of Neven Mrgan and Gizmodo, Microsoft is “all in.” All in “the Cloud,” that is, though the poker metaphor of betting the company on an all-or-nothing strategy seems apt.

Reading some of Steve Ballmer’s vacuous corporate speak surrounding this campaign (including the following PowerPoint-ready bullet points), I am not overwhelmed with enthusiasm for the endeavor:

– The cloud creates opportunities and responsibilities
– The cloud learns and helps you learn, decide and take action
– The cloud enhances your social and professional interactions
– The cloud wants smarter devices
– The cloud drives server advances that drive the cloud

My perspective on this kind of “communication” (such as it is) has evolved over time. When I was 25, it intimidated me, because I didn’t understand it. When I was 30, it annoyed me, because I realized there was nothing to understand, and it was just wasting my time. Now, at 35, it worries me, because I realize that this is how the people who are running things — important things like Microsoft, for crying out loud — actually think. They write nonsense like this and think it’s meaningful.

I wouldn’t bet on that.

Update: In Ballmer’s defense, the full presentation provided a lot more details than this bullet list, but it’s still a lot of not really very much.

Twittegration (or… uh… something like that)

Yes, I should inaugurate this new feature with a profound, witty, or at least marginally purposeful post. Alas, I might as well just say “Hello world!”

This post is a test of a new Twitter integration I’m trying out, using the Twitter Tools plugin for WordPress. Here goes (hopefully not) nothing!

Update: Looks like it works. Now I just need to get my custom URL shortener integrated into it all.