Forum Replies Created

Viewing 1 replies (of 1 total)
  • Thread Starter mrfsrf

    (@mrfsrf)

    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:3000http://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)