That sounds like an issue with your theme rather than a WordPress core one. Put it this way – you’re the only one having this problem yet lots of people use CPTs.
I’m not necessarily saying it’s a problem with core. It might just be that the documentation needs updating.
It may well be that it’s my “issue with my theme” for naming my post type “action”, but I’m not aware of anywhere that tells me that calling a post type “action” is a bad thing to do.
The alternative view is that calling a post type “action” shouldn’t cause this problem, in which case, something in the core is broken.
In case you’re wondering, the process I went through with diagnosis was:
– disable plugins one-by-one (error still present with no plugins enabled)
– change theme (error no longer present)
– change back to my custom theme (error re-appears)
– scan theme code for filters that might affect the query (like pre_get_posts – no filters present)
– disable PHP includes one-by-one (each CPT and custom widget is in a PHP include)
– eventually find that post type called “action” was the issue.
I’m a pretty experienced dev, I’ve used CPT’s a lot, and this is the first time I’ve come across this issue. But it IS an issue. I was hoping someone might validate it for me and let me know if I should raise it on trac or not.
Thanks
Ross
It may well be that it’s my “issue with my theme” for naming my post type “action”, but I’m not aware of anywhere that tells me that calling a post type “action” is a bad thing to do.
That could well be the problem. Have you tried using something less generic?
Well, yes. I’m going to change my code to do that. But my point is that if “action” isn’t listed in the codex as an identifier that you shouldn’t use (and, as far as I can tell, it’s not) then I should be able to use it, and I can’t.
So either:
– I’m not looking in the right place in the codex; OR
– codex needs updating to list “action” as an invalid post type name; OR
– codex is right, I should be able to use it, and core needs fixing.
Could use:
a) validation that calling a post type “action” breaks things the dashboard post search
b) some direction on how to get either codex or core fixed
Thanks
my point is that if “action” isn’t listed in the codex as an identifier that you shouldn’t use
Neither is it mentioned that you shouldn’t prefix your functions with wp_. Or that you shouldn’t use post, page or attachment as names for your CPTs. It would be a practical impossibility to try and list every reserved term in an application the size of WordPress.
Neither is it mentioned…that you shouldn’t use post, page or attachment as names for your CPTs.
Well, I’m gonna have to disagree with that statement: http://codex.wordpress.org/Function_Reference/register_post_type
Look, I spent about 2 hours debugging this last night. I’ve taken time to post a detailed explanation here this afternoon. I’m just trying to save someone else the hassle of having to do the same work again.
If you think this is a “reserved term” and not an issue with the core can we just add it to the list? Can I submit a change to the codex somehow? What should I do?
If you have found that action is a reserved word, then please feel free to update the Codex page yourself. The Codex is a community project. Everyone is a potential editor.
Ah yes. I was already logged in to forums and didn’t realise I had to log in again to edit the codex. I was looking for an edit button that wasn’t there. Done!
Thanks for your help esmi!
Ross
