We don’t have any sort of import for this. The biggest thing to keep in mind is that all of the data already exists in the database. What needs to be done is simply change where the taxonomy is being registered. If it’s just a snippet of code somewhere in a theme or custom plugin, then best step would be to set the same settings in CPTUI for each parameter. If it’s a different plugin that also provides a UI, you’ll want to do the same thing with matching the settings provided there.
Once done, I’d temporarily remove the original source and make sure things are still registering to match before removing the original source for good.
All Custom Post Type UI does is provide a click interface to set the parameters to use, we don’t store anything anywhere special, making everything rather flexible.
Thread Starter
nowton
(@nowton)
If I understand correctly I just recreate everything in CPTUI, then disable the original source, then check whether everything’s working correctly (in the backend, templates would need to be updated of course). Thanks, I’ll try that (in a dev environment)
Yep. Ultimately CPTUI is a collector of saved values to pass into the register_taxonomy() and register_post_type() functions. Should be pretty straightforward to move from one source to the other.
If your current spots are just code snippets that do the registering for you, then you should be able to use the “Get Code” section to compare results of the migration. If you’re using someone else’s plugin/UI, may not be as easy.
