Title: redcooper's Replies | WordPress.org

---

# redcooper

  [  ](https://wordpress.org/support/users/redcooper/)

 *   [Profile](https://wordpress.org/support/users/redcooper/)
 *   [Topics Started](https://wordpress.org/support/users/redcooper/topics/)
 *   [Replies Created](https://wordpress.org/support/users/redcooper/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/redcooper/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/redcooper/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/redcooper/engagements/)
 *   [Favorites](https://wordpress.org/support/users/redcooper/favorites/)

 Search replies:

## Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[AI Translator for Polylang] ACF / SCF Flexible Page](https://wordpress.org/support/topic/acf-scf-flexible-page/)
 *  [redcooper](https://wordpress.org/support/users/redcooper/)
 * (@redcooper)
 * [3 weeks, 5 days ago](https://wordpress.org/support/topic/acf-scf-flexible-page/#post-18909681)
 * Hi [@jerzytraczynski](https://wordpress.org/support/users/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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[AI Translator for Polylang] ACF / SCF Flexible Page](https://wordpress.org/support/topic/acf-scf-flexible-page/)
 *  [redcooper](https://wordpress.org/support/users/redcooper/)
 * (@redcooper)
 * [4 weeks, 1 day ago](https://wordpress.org/support/topic/acf-scf-flexible-page/#post-18906524)
 * Hello [@jerzytraczynski](https://wordpress.org/support/users/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

Viewing 2 replies - 1 through 2 (of 2 total)