Our team is redesigning a website that we have acquired.
The original site used WPML to translate the site (EN&FR).
The site used ACF and also had some custom block (non ACF block).
We created a new design and developed the redesign of the site with ACF blocks.
As the site did not used ACML to translate the acf fields group, we had to create the acf feilds groups in both EN and FR.
So far so good.
But without ACFML, whenever we want to edit a ACF block fields that has repeater fields on a translated page (FR), the content of the repeater fields get lost.
I am aware that this is an expected behaviour withotu using the ACFML plugin.
So I plan to install ACFML for to fix this issue.
Are there any challenges that I should be aware when switching to ACFML?
Currently the sote has around 40 ACF blocks with fields group translated in both EN and FR and we have already created a lot of content in both FR and EN.
I managed to keep the same field names in the acf fields groups while developing the new ACF blocks but the fields keys are different between the translations.
When saving the fields groups locally in acf-json folder, we currently have 2 sub-folders: en/ and fr/.
Some of the blocks and a few acf fields assigned to some CPT, that were already on the site, have different fields names though.
What steps or methodology do you recommend to migrate the setup to ACFML?
If you have any further questions,. please let me know!
There are no settings for ACFML. It is a bridge plugin that must be activated when using WPML and ACF. Otherwise, translation of custom fields is prone to failure.
You asked: "Are there any challenges that I should be aware when switching to ACFML?"
The only challenge I can think of is how you constructed things with ACF, which I'm unsure will continue to work when you activate ACFML.
Thanks for the details.
I will block a good chunk of time in the near future to have a deeper look.
This is going to be a challenging solution to remap everything.
Please leave this thread available when closed 🙂
