Hi @swinggraphics
Wanted to chime in and say that we definitely know and acknowledge that we’re not a full 100% parameter compliant plugin, but we do definitely handle quite a lot of them out of box.
Some of those parts above that you mention are new-er and definitely willing to get them added, like rest_namespace
, register_meta_box_cb
etc. Some we handle behind the scenes by default like map_meta_cap
and most of the itemized rewrite
parts. Some, we just admittedly haven’t put in to the core plugin like the capabilities part. I have my own addon for that which I believe should still work, but I’ve never managed to find a chance to real time test it.
That said, we also have a lot of filters available to users, so that they can receive the arguments for a given post type, and fill in spots that we may have missed or are admittedly missing. This would allow to still use CPTUI for the overall registration, but spot fill as needed. I have provided the links to those filters at the end of my reply here.
As you mention some of the parts you noted as missing aren’t as common, and that’s definitely a contributing detail for why we haven’t included them. We aim to be a great middle ground that covers 90-95% of use cases.
That said, I am also going to add new enhancement issues for some of the items you highlighted, if I don’t already have an issue open already, so that we can get those in a future version.
Post types:
https://github.com/WebDevStudios/custom-post-type-ui/blob/1.11.1/custom-post-type-ui.php#L530-L540
Taxonomies:
https://github.com/WebDevStudios/custom-post-type-ui/blob/1.11.1/custom-post-type-ui.php#L763-L775