Hello @frisbee9580
I believe this feedback refers to a support ticket that our team discussed internally at length. You are right, it was frustrating on both sides not to be able to reach a definitive technical explanation, despite the time invested.
For clarity, here is a summary of the issue and what was investigated on our side. You reported an inconsistency when using machine translation with nested ACF blocks: in some cases, child blocks inside a parent ACF block (using InnerBlocks) were not sent to DeepL, especially when the parent block had no ACF fields of its own. You also observed that adding a “dummy” ACF field to the parent block worked around the issue on your side.
Throughout the ticket, our support team clearly identified your scenario (a parent block without ACF fields using InnerBlocks to contain ACF child blocks). To better understand the issue, we attempted to reproduce it in our environment. Despite using your files and our internal “Dumper” tool (to inspect what content was sent to DeepL), the issue never occurred on our test environments. The strings were consistently sent for translation.
Without being able to reproduce the behavior on our side, it becomes extremely difficult to identify and fix a potential bug. In such cases, having access to a full site copy can be very valuable, which is why we suggested investigating further on a duplicated version of your site, of course with your agreement.
We understand that you identified a workaround and chose not to pursue further investigation at that time. That said, we remain fully available to help and would be happy to continue the investigation using a copy of your site. We are genuinely interested in understanding the root cause of this issue, as it has been puzzling us, so please do not hesitate to contact us.
Best regards
Your response is actually a great example of my complaint about the quality of support.
I reprod the issue on a stock wp-env dev environment using the official wp-env package with a full repro video, and described my use of the wp-env package. Your support team should have understood that and taken initiative to spin up a wp-env environment themselves. There was never a need for a copy of any of my dev/staging/prod sites. The repro video provided by your support team did not follow what my video did closely.
