Instead of copying the code of custom fields and embedding it into a website, the export and import features we’re going to talk about in this post will help you to do that without touching the code. This method has the same advantages: synchronizing custom fields between sites, easy back up, and saving the setup time. But, there is a difference. If you don’t know where to embed, edit, or save code as instructed in the previous post, this method can help you to do them all.
Now, you know what custom fields is and in the previous post, we stopped in the step “WordPress calls the
update_metadata function to store data from custom fields in the database”. In this post, we’ll follow up that flow to figure out how WordPress organizes the database.
Bunching custom fields aim to rearrange the related custom fields into one group. For instance, one group of contact information contains related custom fields such as name, phone number, address and email. Grouping may make the custom fields look better and more logical when they display. In addition, it brings some other benefits of organizing data afterward.
Until now, we’ve known what custom fields is and how to use the functions provided by WordPress to work with custom fields. You’ve prepared everything needed to develop practical applications. But wait, before embarking on doing something new, you had better dig a bit deeper to have thorough understand custom fields’ nature. It’s time to find out an answer to the question: “What really happens with custom fields when I click Save post?”. The two coming posts will give you the answers.
If you regularly work with many different projects in website development, especially the projects have the similar custom fields, this post will be useful for you. This guide will bring you an easy way to copy meta boxes and custom fields from one site to others with our Meta Box Builder.