Hello,
did you find a solution for this?
I need to do exactly the same thing as I have a lot of repeater fields and flexible content which is blowing my database.. but I cannot find a solution.
My first Idea was to find empty fields and check for the saved value and unset it in $_POST[‘acf’] if it was empty before as well. But I had to abandon this because it did not save if somebody deleted a repeater field.
My second idea then was to get 2 arrays old and new and compare the values
but this is not working because one uses keys the other names and the structure is not the same 🙁
Hello,
Did you find a solution? Having similar trouble with this.
..
Just found the solution for my problem with date fields inside a repeater field.
Maybe this will help somebody else too:
'meta_query' => array(
array(
'key' => $repeater_date . '_%_date_time',
'value' => array( $min_date, $max_date ),
'compare' => 'BETWEEN',
'type' => 'DATE',
)
)
Hi Elliot,
the meta_value in wp_postmeta was saved like this: 2015-11-10 20:00, so this is not a problem.
The problem was, that the default value of the new field date_time_picker is “16/06/2016 1:42 am” and not “2016-06-16 01:42:02”.
I changed this now with my fields which use the date_time_picker, but it was quite a hassle to update all my projects.
Me too. Temporary Downgraded to Version 5.3.3 to import my fields correctly..
Hello James,
thank you for your reply. I did as you suggested and found out that the problem was caused by a plugin (Advanced Custom Fields: Contact Form 7 Field). I had integrated it in my theme so I was able to commented the lines which caused the trouble out:
$(".cf7-select").select2({
width: '100%'
});
Since this is only showing a more fancy select dropdown in backend it’s causing no harm :).
I still don’t really understand the problem behind it as it was triggered by the new ACF Pro Version.
Thank you for your help
Britta
I just had the same wish: “Simply overwriting a json file every time i make a change to the custom fields would be super!”.
In my case I found out that the exported json-file had these [] brackets at the beginning and ending of the file and the sync-file did not.
So I just took my exported json-file and deleted the brackets in the first [ and last ] line and then it was loading.
I hope this helps somebody :).
Would be nice if the files would be identical though!
Fantastic. What a fast reply :).
Yes it’s working now for me.
Thank you!!
I am having the same Problem. With Version 5.2.9 it’s still not solved. Tested it with the first Version 5 and there it is also not working.
When I used the old PlugIn (not Pro) it is working (but I’m not downgrading for sure 😉 ) So I hope there will be a solution soon. Thank you
