Background of the issue:
I am trying to delete an ACF flexible field block on the content page within the base language. The block gets deleted in the base language correctly. Since I use automatic translations, I now click on the translation editor and the overlay opens – the deleted field is not visible anymore, which is correct. Now I save the translation.
Symptoms:
If I now go on the translated page, the deleted block is still there and did not get deleted!
Questions:
Why is the deleted block still visible on the translated page?
How can I ensure that the deleted block is removed from the translated page as well?
The bug exists after the initial troubleshooting steps. So the ticket is escalated to our second-tier team for further debugging. We will get back to you as early as possible. Please wait.
As of now, this is an expected behavior. ACF does not delete fields and their data from the database when they are removed from a post. It only deletes them when the post itself is deleted.
For more details, please refer to the following link and attached images: hidden link
The only workaround for now is to manually remove the deleted fields from the wp_postmeta table after taking a full site backup (mandatory).
This ticket has been escalated to our developers for further investigation. A fix for this issue will be included in a future version of the ACF Multilingual plugin.
Thank you for the updates. This bug will be fixed in the upcoming version of ACFML, mostly in the 2.2 version. It is still in the development stage, we will get back to you soon when we have an update from our developers about this.
As for the workaround with editing the database: It may work, but it's just not an option for us. We cannot possibly expect from our team to always edit the wp_postmeta table when changes are made. But thanks for the suggestion.
We hope to see the new release soon! Have a nice week!
Thank you for your feedback. We will get back to you as soon as we have any updates from our team. We appreciate your patience and understanding. Please wait.