You have to create the custom posts by hand, one by one, from the admin. If you import them bulk, the custom table will not be updated. I have a custom post already created that I want to transfer to custom table; if I go to a post and update it, nothing happens, the data is not saved in the custom table.
First of all I want to thanks the author of this amazing plugin… we have a meet call where he explained to me some really usefully tricks to import a large database in his custom table, saving hours of working. This plugin is a must for anyone who use ACF. Also it works perfect with the JSON method from ACF. Nothing if more fast than this combination…. Again thanks and thanks 😄
Absolutely a 5 star plugin.
Now why did I say "Excellent Start"? Because it does not support the Repeater field, which is almost a necessity for almost any serious ACF (Pro) project. Any project that uses the Repeater field won't be able to easily export all the Custom Field values, it will only see faster query executions. I hope this will be added in the future... but I do understand the difficulties in coding to support such functinality.
Update: I just checked the official Documentation page, it it says it does support the Repeater field, which is not listed in the Description of this site... so I need to test it to find out which one is true... there are 2 conflicting statements here...
Latest Update (after initial review): After further testing, Repeater fields are NOT supported, unless I'm doing something wrong, the documentation is definitely wrong !
Conclusions: Out of the box, extremely easy to setup, works like a charm by testing only few of the supported fields, and there are plenty of them. That said, I also wonder if there is a way to make it support 3rd party ACF fields, as the ACF eco. is quite large and there are a number of 3rd party custom made ACF fields that some of us use.
The Read Only feature is an interesting one too, only Admins can edit that. I'm involved in another plugin that can make a field a Read Only, and in that case it is really a Read Only, nobody can edit it, so this take is way better !
Another interesting note: I think the Custom Fields by default also get stored in the Post Meta table as well the custom Table be create for them. Thankfully there is a filter to stop this behavior for those who want it. Obviously I need more time to read all the Doc pages and do more thorough testing in a few days...
I absolutely love what I have experienced so far,
Soon, I will come back here and give a verdict on the Repeater field, and clear things up !
Thanks a million,