Conversation
supportHi, I’m running into a serious issue when using Polylang AI Translator together with SCF (Secure Custom Fields, ACF clone) and a Flexible Content field . When I try to duplicate/translate a page that contains a Flexible Content layout: With Gutenberg enabled → I get a white screen (fatal error) With Gutenberg disabled (Classic Editor) → the page loads, but I can see that the error is related to the Flexible Content section Additional details SCF is used instead of ACF, but it should be fully compatible (same structure) Translation duplication plugin works correctly The Flexible Content includes multiple layouts and nested fields (text, WYSIWYG, etc.) Any idea on how to resolve this?
Hello @jerzytraczynski When you get a chance can you please share more details about this bug. Like what plugins do you use and what is your post/page content and also if you could share some screenshots about this issue. We are looking for some more details to reproduce this issue. Thanks
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.
Hello @jerzytraczynski When you get a chance can you please share more details about this bug. Like what plugins do you use and what is your post/page content and also if you could share some screenshots about this issue. We are looking for some more details to reproduce this issue. Thanks
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.