I’m pretty certain that that’s how custom post type URLs are regardless of registered with ours or via functions.php. It’s nothing we’ve set up ourselves in the plugin. We really don’t do anything with permalinks outside of passing in post type and taxonomy parameters related to them, for register_post_type() and register_taxonomy().
Permalink customization falls outside of what we focus on.
I’m not sure this would be permalink customization, as much as CPT UI rewriting what has already been customized.
I have post categories that show up with a visible subcategory in the link, but it seems that the custom post types created with CPT UI just won’t do this. They won’t show the subcategory – they are overwriting the default URL, and there doesn’t seem to be a way around this.
Ultimately what CPTUI does is collect and store arguments that get used for register_post_type() and register_taxonomy() and pass each saved type/taxonomy into those functions on the init hook. Priority 9 for taxonomies, priority 10 for post types. We don’t do any custom rewrite rules or permalink manipulations other than flushing rewrite rules on save so that new object types can be properly acknowledged.
If we’re still doing something wrong here, then I’m willing to hear someone out, with example spots, as I’d prefer to get it right than not.
Hi Michael,
Thanks for the reply, and let me say – awesome plugin. I really appreciate the work you’re doing on it.
I don’t think you’ve done anything “wrong.” The plugin is obviously really good.
I think the simple issue is that when a user sets up a custom taxonomy to be exactly like a category then sets up a custom post to be exactly like a post – it’s confusing that the permalinks that are already setup don’t work exactly the same way. I understand your argument, but the typical plugin user won’t understand what you’re getting at. They will simply be confused that they have no way (within your plugin) to get their subcategories to show up in a posts permalink, as the first author on this had written.
In other words, if I have http://mysite.com/awesomecat/bestsub/coolpost/ under the regular WordPress posts and categories that would be the category “awesomecat” which is a parent to “bestsub” and the post “coolpost.”
Using only CPT UI, I can’t do that. I can only get http://mysite.com/awesomecat/coolpost/
If you are resolved not to include it the ability to adapt the permalink for custom posts, so be it, but I do think it’s an integral part of it, so it makes the plugin a bit incomplete not having it.
If anyone else is trying to work through this issue, I found that the plugin “Custom Post Type Permalinks” works very well with CPT UI.
Would the same things be occurring if one was registering these custom post types themselves via functions.php?
I’m not arguing against you by any means, but I am going based on how WordPress behaves with regards to custom post types. Posts and pages both get some special treatments that aren’t made available out of box, or at all with CPTs.
I get rewrite/permalink questions regularly, and it’s not an easy topic to cover, as everyone is going to have different needs. I realize there is demand, but it’s easy to potentially screw things up.
Ultimately it’s just a matter of what we want to try and incorporate and what we want to leave to other plugins/developers/what have you.
Fair enough – the answer is yes, of course.
I can respect what you’re saying, especially with a free plugin that works very well at what it does.
Thanks for your time.
FWIW, I’m not against the idea of exploring and incorporating both rewriting and capability customization, which is another weak area of CPTUI. I’m also not confident at the moment, that I’d be able to release anything that is both flexible enough for the various scenarios, while also working each time. It’d need exploring and testing and better understandings of all involved. So, there’s room for growth here for myself.