Reply To: WordPress 3.6 Revisions: custom fields no longer tracked

• zevisternlicht

• September 26, 2016 at 11:12 pm

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.