Hi @marcusdeman
Did you customize the REST-based fields for this given post type at all? or did you leave them all defaults/empty?
I just realized where this is coming from. “News” is already an existing CPT registered via php.
How am I able to define it in CPT UI as well? When I do that, I get this message:
“Please choose a different post type name. news matches an existing page slug, which can cause conflicts.”
You should have a “I’m trying to migrate things in to CPTUI, let me save this” checkbox below the singular label, that will allow you to save anyway.
I have selected that option but still getting the same error message…
I think we need to patch up some small js bugs.
In the meantime, you could temporarily comment out the current post type registration spot so that it’s momentarily not registered, so that you could save the same within CPTUI.
Yes I’ve tried commenting out the post type registration as well but CPT UI still shows the same error message unfortunately.
Ahh, I mis-read a bit with the last error you presented. that error is indicating you have a page named “news” already, not a conflicting post type at the moment.
I think the best workaround we have for that, if really wanted, is renaming the page slug temporarily, saving the post type in CPTUI, and then re-renaming the page back to where it was.
However, there’s some risk with doing that because URLs may or may not be interpreted as child pages rather than posts in their intended post type.
