Okay
  Public Ticket #1392486
Issue while saving a content with Visual Composer
Closed

Comments

  • mybusiness360 started the conversation

    Hello I notice that with the new wordpress version there is an issue while Im trying to save a content with VC.

    With Firefox I get 2 JS error :

    1. TypeError: a is null   tinymce.min.js:29:18262
    2. TypeError: c is null    load-scripts.php:676:4843


    Tested with Firefox Quantum 57.0.1 ( Arch Linux ) and 57.0.1 ( Windows 7 )


    In both Chromium and Chrome it does save the content BUT it scroll us at the bottom of the page all the time, making it impossible to work efficiently.

    We use the latest Version of Silent 8.5.3

    Any idea on how to fix this ?

  •  9,017
    Tahir replied

    Hey Again,

    Yes Firefox seems to have a bug thats causing this . Try using Chrome instead . 

    Be.st


    ThemeNectar Support Team 

  • mybusiness360 replied

    But there is an issue on Chrome / Chromium too ( both Linux & Winblows ).
    Whenever we click save button it always goes on the footer of the page. Im working on translations atm and we have over 50 sections on every page. Its impossible every time I click save on a section to re-scroll on top and try find where I was before.

    Dont you have the same issue on chrome ?

  •  9,017
    Tahir replied

    Hey Again,

    The Scrolling issue was fixed in the latest version .

    Please update to Salient Theme Version 8.5.3 and Salient VC 5.2.4. 

    If you are not seeing the Plugin Update Notification you need to uncheck the " Disable Theme Reccomended Plugin Notifications " Field in "Salient Theme Options Panel"  -> General Settings -> "Toggle Theme Features" Section .

    To get a list of Bug Fixes and new Feature addons in the Latest Theme update,  the changelog can be viewed here : http://themenectar.com/changelogs/salient.html .

    Update the theme by following this guide: http://themenectar.com/docs/salient/updating-salient/ .

    Best.


    ThemeNectar Support Team 

  • mybusiness360 replied

    Updating VC from 5.2.1 to 5.2.4 fixed the issue. Thanks!