Visual Composer / WP Backery Frontend bug

  • I use this great plugin on different pages, it is useful to provide areas of a company that work seperately with their own domain, but still run them in the actual WordPress page.

    What I notice is that the frontend editor doesn’t work correctly when dealing with visual composer ( or today known as wpbackery ). my pages that are switched to a separate domain don’t load in the frontend, or it comes to an infinite load. it would be great if there would be a fix here that recognizes when the website is displayed in a known editor and then doesn’t force the loading over a separate domain.

    Is there maybe a quick fix here?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author matthias.wagner

    (@matthiaswagner)

    hy,

    we will provide enhanced compatibility with page builders in the next version, which will be released in the next weeks. if you are able to do some coding, you could find the part where the request uri is processed and wrap it in a
    if(!is_admin()){...}
    statement. but if it is possible, just wait ??

    matt

    Plugin Author matthias.wagner

    (@matthiaswagner)

    please see the new release and try “enhanced compatibility mode” in the settings ?? please report back if it helps for your page builder

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Visual Composer / WP Backery Frontend bug’ is closed to new replies.