redcooper

Hi @jerzytraczynski,

Thank you for reporting this and for the detailed explanation.

We were able to reproduce the issue with SCF Flexible Content fields. The problem was related to how Flexible Content / nested ACF-compatible fields were being saved after translation. In some cases the layout structure could be written incorrectly, which could cause the editor to show an empty Flexible Content section or trigger a fatal error in SCF when opening the translated page.

We’ve prepared a fix for this. The update improves SCF/ACF compatibility by preserving the Flexible Content layout structure and saving translated/custom field values through the ACF-compatible field API instead of raw post meta.

This should resolve the white screen / fatal error with Gutenberg and the broken Flexible Content section in Classic Editor.

The fix will be included in the next plugin update. After updating, please try translating the page again from the original source page. If you already have a broken translated page, delete that translated page first and create a fresh translation.

Thanks again for helping us identify this.