I had a question about best practices for toolset in terms of development within a staging environment opposed to a live environment and the information that is included in the import / export.
Hi, can you elaborate on your questions? I'll do my best to respond here.
Hi Christian, thanks for the reply back, was hoping to use the chat feature for back and forth. Basically, I just wanted to confirm best practices for toolset on a dev site or the live site. I'm adding a custom post type integration for listings with 300+ listings and was wondering if the import / export feature included all information from the custom post types (photos, info added to custom fields, etc.). Once the views, archive & all custom post types affiliated are set up an admin will be then adding all the content tot he custom fields / listings.
Would a staging environment for development and then pushing the site live be a best practice for Toolset or exporting the types & views from a dev site & then importing to the live site? The site where the integration is being added is already live, so I wanted to confirm which practice would be the most seamless.
Appreciate the help!
Hi, the Toolset Import / Export feature doesn't export content for custom fields, it exports structures. So if you want to export all the custom field settings and options, Views, Content Templates, post types, and so on, that's ideal for the Toolset Import / Export feature. If you want to export information stored in those fields for each post, like custom field values, then you should use the WordPress Export tool or another 3rd-party plugin for exports.
You could also consider a migration tool, like Duplicator. A good migration tool will come with robust text replacement features, so you can manipulate domains easily without worrying about serialized data.
My issue is resolved, I'll be using a staging environment. Thank you!
