I was inattentive. I had made a reference in functions.php of my theme based and only realized now. When I exported the fields and content to another topic, the site where work conflict was also imported.
Now, it seems that everything is working properly. Sorry the confusion!
I’m still on localhost ( XAMPP 1.8.0 [PHP: 5.4.4]) to build the first theme that will be used in WPMU web. What I did:
1. I installed WP 3.5, created the CTP and its taxonomies.
2. I created custom fields co ACF 3.x.
3. I upgraded to WP 3.6 and 4.2 ACF
4. Found errors: infinite loop fields, display fields all posts not only in local set.
5. Removed fields via plugin and did not use php code in functions.
I am creating a website for WPMU institution, subsites and subsidiary organizations will share the same theme. I understood that adding the codes to the functions.php become simpler using the fields without creating them on every site that uses the theme on the network.
I appreciate your response.
Unfortunately I did not understand exactly what to do and what to migrate in mudandaças should do manually indicated in the table of actions and filters. The text says that it is easy to migrate, and indicates http://www.advancedcustomfields.com/docs/tutorials/creating-a-new-field-type/ this link to learn more, but does not work.
So I found it easier to remove the 15 fields created and recreates them on the same site. There was no reference to them in functions.php and I believed that the simple removal of the fields via plugin erase the references in the database.
Maybe relamente easy for those who are accustomed to the plugin and meet the English language perfectly, my English is not fluent.
Thanks for the help!
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.