Home › Forums › Bug Reports › WordPress 3.6 Revisions: custom fields no longer tracked › Reply To: WordPress 3.6 Revisions: custom fields no longer tracked
I didnt manage to fix it.
What I did was to create a new field called Change Summary (possible as the main content even), and each time I changed anything I updated it. This forced a new revision to be stored.
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.