Okay
  Public Ticket #3488652
WPBakery Empty windows
Closed

Comments

  • Dung started the conversation

    Hi there; 

    I am working for a client and I encountered a problem within Salient that hasn't happened to me before: When I Edit pages in either Backend or Frontend all windows from WPBakery appear completely blank, unless there is a tab that I can click back and forth until the contents to edit appear. But if there is only one field to edit, the contents never do apear in the window. 

    I have done my due diligence and de-activated all third party plugins, check for updates and clear the cache to no avail. I deleted and re-installed Salient as well. Is there any other option that I can try to fix this problem?


    Thank you very much beforehand. 

    Attached files:  01.png
      02.png
      03.png
      04.png

  •  1,877
    Judith replied

    Hi Dung,

    Thanks for writing to us.

    I request you allow us access to this issue from your end by providing us with your admin login details, if you are not comfortable with that, you can create a staging site with identical settings as the live site and then share the login details.

    I look forward to hearing from you.

  •   Dung replied privately
  •   Dung replied privately
  •  1,070
    ThemeNectar replied

    Hey Dung,

    The issue is occurring because the main script responsible for handling events in the edit form is not loading in your setup. The file I'm referring to is:
    https://legback.com/wp-content/plugins/js_composer_salient/assets/js/dist/edit-form.min.js

    This file is included in the same response as the edit form contents when the settings popup loads. However, in your setup, the path is being changed to a relative location instead of the default absolute path. Here's a screenshot of the edit form response for reference in your setup:

    9627297020.png

    It looks like most of your admin URLs are being switched to relative paths. I would suspect that this is due to some sort of custom underlying directory structure for your WordPress instance.

    To correct the issue, the URLs would need to be switched back to the default absolute structure. If you didn't implement this change yourself, I would recommend reaching out to your hosting company for assistance in resolving this issue.

    Kind regards