Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author codepeople

    (@codepeople)

    Hi,

    I’m sorry for the delay in respond to your question, I’ve not received the notification about your ticket.

    The forms builder is generated with javascript, but if there is an uncaught javascript error in your page, maybe by a conflict with another plugin installed in your WordPress, the rest of javascript code in the page will stop, and the forms builder will not be loaded.

    Unfortunately, I cannot detect the issue from an screenshot. Could you send me the access to your WordPress to my private support page to check the issue in detail, please?

    http://wordpress.dwbooster.com/support

    Best regards.

    I had the same problem and turning off the plugin “Layerslider WP” solved the issue. jfi.

    Plugin Author codepeople

    (@codepeople)

    Hi andohean,

    I’ll install the “Layerslider WP” plugin to check the conflict.

    Thank you very much for sharing your solution.

    It works when I remove the option “Use Google CDN version of jQuery”.

    Thanks anyhow for your reactivity!

    Plugin Author codepeople

    (@codepeople)

    Hi andohean,

    Yes, the conflict can occur if the jQuery framework is loaded from the Google CDN but in an incorrect mode.

    The wp_enqueue_script function of WordPress, used for loading the javascript files on website, accepts a parameter to define that the scripts in the plugin are dependent of other scripts. In the specific case of our plugin, the form builder depends of jQuery.

    So, the correct, in the case of plugins that prefer to load the jQuery framework from the Google CDN, instead of the version distributed with the WordPress, is calling two functions:

    wp_deregister_script( 'jquery' );

    to break the link between the “jquery” handle, and the location of file in WordPress, and then calling the “wp_register_script” function for registering the ‘jquery’ handle again, but from the new location of the file.

    I’ll check our plugin in a scenario like yours, and publish an update in consequence.

    Best regards.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Back End Issues After Upgrade’ is closed to new replies.