Okay
  Public Ticket #2807859
WPBakery Not Working
Closed

Comments

  •  1
    agriffes started the conversation
    June 21, 2021 at 11:31pm

    When I try to open frontend page editing with WPBakery, the WPB logo shows up and the editor does not load.

    So far, I have:

    1. - updated Salient Theme (v 13.0.5)
    2. - updated Salient WPB plugin (v. 6.6.0)
    3. - Disabled Gutenberg in WPB settings
    4. - Deactivated other Plugins
    5. - Cleared cache
    6. - Tried in Safari and Chrome

    Could you please advise?

  •  279
    Noah replied
    June 22, 2021 at 5:16am

    Hello there,

    Thank you for contacting us.

    Please try installing the "Clasic editor" plugin and see if the issue will be solved.

    Let me know how it goes.

  •  8,847
    Tahir replied
    June 22, 2021 at 6:59am

    Hey Again,

    Please check for Browser Console Errors : https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    Thanks 

    ThemeNectar Support Team 

  •  1
    agriffes replied
    June 30, 2021 at 1:16am

    Tried installing and activating Classic Editor Plugin, and the issue has not resolved yet.

    @Tahir - the Browser Console Errors website appears to be a broken link.

    Thanks all for your support so far.

  •  8,847
    Tahir replied
    June 30, 2021 at 7:17am

    Hey Again,

    Please see: https://developer.chrome.com/docs/devtools/console/log/ . 

    Thanks

    ThemeNectar Support Team 

  •   agriffes replied privately
  •  8,847
    Tahir replied
    July 1, 2021 at 6:22am

    Hey Again,

    This seems like a Cross Origin Issue therefore you would have to contact the Hosting Provider and have them adjust the Server Settings. 

    Also this might help: 

     

    Thanks

    ThemeNectar Support Team 

  •  1
    agriffes replied
    July 1, 2021 at 9:12pm

    Thanks Tahir - I have managed hosting, so I have the support team looking into the Cross Origin Issue.

  •  1
    agriffes replied
    July 14, 2021 at 7:21pm

    Thanks to all who replied on this thread - it was indeed an issue with JavaScript and my hosting provider was able to resolve it with the suggestions you made.