Visual Composer and Ajax Search

Home Forums Product Support Forums Ajax Search Pro for WordPress Support Visual Composer and Ajax Search

This topic contains 1 reply, has 2 voices, and was last updated by Ernest Marcinko Ernest Marcinko 8 years, 3 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #7454
    Kyle Bailey
    Kyle Bailey

    When using Ajax Search Pro 4.7.0 with Visual Composer 4.9.2 the text within the backend visual editor in VC is white in colour and includes snippets of code.

    I have added this which I noticed you posted to eliminate snippets of VC code showing up in search results and I’m guessing that this may have to do with it but perhaps not. This code did eliminate the VC code showing up in the search results so hopefully these both can/have been resolved.

    /* Fix VC Code showing up in Search */

    function asp_force_load_vc_shortcodes( $post_ID ) {
    // VC 4.6+ fix: Shortcodes are not loaded in ajax responses
    if ( method_exists(“WPBMap”, “addAllMappedShortcodes”) )
    add_action( ‘asp_before_search’, ‘asp_force_load_vc_shortcodes’ );

    /* End Fix VC Code showing up in Search */

    Ernest Marcinko
    Ernest Marcinko


    That shortcode problem fix is already included with the current version (4.7).

    I’ve checked your site, and the problem is that ajax-search-pro is installed in the incorrect folder. It’s in “wp-content/plugins/ajax-search-pro 4.7”, while it should be “wp-content/plugins/ajax-search-pro”.
    That causes missing file references and it’s causing that problem in the Visual Composer back-end editor.

    Please de-activate and delete the plugin completely, make sure that the “ajax-search-pro 4.7” folder is deleted, and install it via the plugin manager so it’s put into the correct folder. If you update the plugin next time via SFTP, make sure to not rename the folder – or if it was renamed by a 3rd party plugin, make sure to not use with with ajax search pro.
    Renaming or installing plugins in different plugin folders can cause plugin malfunctions.

    I’ve also noticed other asses related and javascript related issues on the console, which may cause trouble in the future:

    Currently they doesn’t seem to affect the back-end, but you can never know.

    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.