Types 0.9.3 Imports Settings from Other Plugins

Types 0.9.3 is out. This release can import your existing settings from Custom Post UI and Advanced Custom Fields. It also streamlines the post-edit screens and fixes a bunch of bugs.

The most important feature for this release is the ability to import from other plugins.

If you have existing sites that use Custom Post UI, for defining custom post types, or Advanced Custom Fields, for custom fields, you can now seamlessly migrate the to Types.

Go to Types->Migration (which is only available if one of the above plugins is also enabled).

You’ll see a summary of what’s available for migration.

Migrating settings from Advanced Custom Field plugin

What happens after you migrate?

If you’re migrating custom post type settings from Custom Post UI, plugin will deactivate it immediately after the migration. This way, you don’t get the same types and taxonomy defined twice (which will cause errors).

When you migrate from Advanced Custom Fields, the plugin remains active. You may need to do some small touch-ups, like tell Types where to display the newly imported meta boxes. When you’re done, you should manually deactivate Advanced Custom Fields.

Each of these plugins stores its settings in a different place in the database, so this migration process doesn’t alter the original settings of the other plugins. You can experiment with Types and if you’re not happy with it, you can always go back to the other plugin.

Other improvements and Bug fixes

Types 0.9.3 includes other features which you may like.

We’ve streamlined the post-edit screens and removed some stuff which is pretty useless and just took up valuable screen space.

We also improved functionality with WPML, highlighting custom fields which WPML will synchronize between languages and warn when WPML’s settings override Types settings.

And, no version is truly complete without crushing a few bugs. Types 0.9.3 fixes several compatibility issues with different servers and other plugins and makes the custom field editing screen way way faster (due to some SQL optimization work).


You can get the current version of Types either from your wp-types.com account or from the Types page.

We’d surely appreciate it if you can go and rate Types:

You can download it from Types page.

How is it working for you?

Upgraded to Types 0.9.3? Leave a comment here and tell us what you think!

6 thoughts on “Types 0.9.3 Imports Settings from Other Plugins

  1. James

    Seems pretty cool. Set up a bunch of things on the development side, but couldn’t import anything. Removed all plug-ins…nothing. Used different websites/browsers…nothing. I can’t import one thing without getting the same errors every time…and what an unfriendly error it is….

    here it goes….

    Error parsing XML

    xmlParseEntityRef: no name

    Software is completely unusable if i have to set it all up again. Ugh.

    1. Amir

      Looks like something that someone would need to debug. The error report says that the XML is broken. Did you look at the XML to see what it contains?

  2. PH

    Hi. Couple of questions:

    1. Can this import from Custom Field Types plugin? Or just tell me which columns from the wp_post and wp_postmeta tables I should be writing some SQLs for?

    2. Also, more importantly, with just the Types plugin and not the Views plugin, can I “filter” based on a custom field? I want to create a drop down filter on my website, when a user selects an option (values of the custom field) then the page refreshes with only those bits.

    Thanks so much! By far the BEST-EST custom fields plugin. makes WordPress a true CMS.

    1. Amir

      1. Types uses the normal WordPress postmeta table, so there shouldn’t be a problem. The import process is for the definition of the custom fields, so that they display correctly in the GUI. If there’s no import for your plugin, you can still use Types. You’ll just need to define the field types once. You do that in Types->Settings.

      2. Types doesn’t include any content query engine. This is done in Views. If you want to use Types without Views, you will need to write the PHP that queries the database manually.

  3. Carloalberto

    Hi guys, trying to exporting some custom fields from Advanced Custom Fields (ver 2.1.4 and even tried with ver 3.2.5) to WP Types (ver 1.0.1)

    No way to load “Migration” page.

    I get this error

    Fatal error: Call to undefined function wpcf_custom_types_default() in C:\xampp\htdocs\mywp\wp-content\plugins\wp-types\includes\migration.php on line 15

    Any suggestion?
    Thanks in advance.


    1. Amir

      We will need your database to debug this. Can you please post about this in our forum? Our support folks will contact you to get your database for debug.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>