Importing / Exporting all Toolset settings

This support ticket is created 4 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Import and export, Setting up custom fields, Types plugin

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 4 years, 10 months ago.

Assisted by: Christian Cox.

Author

Posts

March 3, 2020 at 7:36 pm #1537777

bobG-3

I have 2 versions of the site, basically the same but one has many different Toolset settings, mainly with the UI. The post types and fields are the same, but some fields are renamed, hidden, etc. I want to take these modified settings back to a development version of the site. If I export them from the most recent one, then import to the other (using the tool at admin.php?page=toolset-export-import), will it just overwrite all the settings? But since the post types and fields are the same, leave the actual content as-is? If not, how would you recommend that I do this? Again, the content is all the same, it's the tool set settings that I want to replicate on the other version.

March 3, 2020 at 9:14 pm #1537885

Christian Cox

Hi, as long as the field slugs didn't change, importing the Types settings back into a development site should be fine. I recommend keeping a backup of your development environment database, just in case you need to revert quickly for some unforeseen reason. But generally importing field settings will not affect the content (as in the field value content), just the settings of the fields. Again, this assumes the actual field slugs did not change. If the field slugs changed, it's not so simple because you have to consider the field slugs and values in Production are no longer in sync with the field slugs in development. It might be more practical in that case to wipe development and start over with a new clone from production.