Title: mrfsrf's Replies | WordPress.org

---

# mrfsrf

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

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

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[TranslatePress - Translate Multilingual sites with AI Translation] WP 6.9 and TRP 3.0.7 Broken TRP Editor](https://wordpress.org/support/topic/wp-6-9-and-trp-3-0-7-broken-trp-editor/)
 *  Thread Starter [mrfsrf](https://wordpress.org/support/users/mrfsrf/)
 * (@mrfsrf)
 * [6 months, 1 week ago](https://wordpress.org/support/topic/wp-6-9-and-trp-3-0-7-broken-trp-editor/#post-18788254)
 * Found a solutiion. Local DEV setup uses Browser Sync in a proxy mode.
 * After upgrading WordPress from 6.3.2 → 6.9, the TranslatePress (TRP) visual editor
   started breaking when running the site through BrowserSync proxy ([http://localhost:3000](http://localhost:3000)
   → [http://localhost:13500](http://localhost:13500)).
 * The TRP editor page (/?trp-edit-translation=true) was throwing:
    - Uncaught SyntaxError: Invalid or unexpected token
    - SecurityError: Blocked a frame with origin … from accessing a cross-origin
      frame
 * Root cause:
    - BrowserSync snippet injection / response modification was corrupting TRP’s
      large inline localized JS payload (trp_editor_data).
    - Additionally, when some TRP iframe/admin URLs resolved to the backend port(:
      13500) while the editor UI ran on :3000, browser same-origin restrictions 
      caused iframe access errors.

Viewing 1 replies (of 1 total)