I have now found your forums.
I suspect this may answer my question:
http://pods.io/forums/topic/convert-wp-types-to-pods/
I will try this out.
Please let us know if that works. I’ve never done this, but the answer I gave there is the best theory I have on how.
Hi Josh,
It is more or less working.
The one hassle is that PODS defaults to using an underscore ( _ ) in the slug, and it is the slug that seems to be the key identifier of each post type and taxonomy type.
Whereas all the other (about 5) customer types plugins I have tried all use a standard hyphen in the slug ( – ) just like the rest of wordpress does.
So, the two word custom types/taxonomies I have are very difficult to get PODS to pick up on. After multiple attempts it did pick up on one of my types with a two-word name, despite failing to a few times, and despite it PODS using an _ and the existing type using a -.
Is there a reason PODS uses underscores in the slug, even though the rest of WP uses hypens?
Joanthan
I honestly couldn’t tell you, that’s a decision that was made years ago. That said, if you extend an existing post type, with a hyphen in the slug, Pods will not change it.
Do I get exactly the same functionality and level of control when extending an existing post type (or taxonomy type) as I do when creating it from scratch in PODS (or having PODS pull in an existing one, as though created in PODS) ?
Here what I ended up doing. So far, so good.
I went into the database and manually changed all my hyphens into underscores.
I then set a customer slug on each tax and type using a hyphen in place of the underscores. So, “custom_tax” ended up with a slug of “custom-tax”, etc. So far this seems to have done the trick.
WordPress uses hyphens in url slugs, but not in its content types. It uses underscores such as post_tag, and field names use underscores too for all meta key and option names that I’m aware of in core. We normalize to underscores as a legacy to Pods 1.x and to retain support for table-based Pods, since hyphens are not acceptable for table names or column names in the DB.
