[Support request] vc_user access is not defined conflict

Please login to receive premium support.

Support for the free plugin can be found here.

Home Forums Pro Support vc_user access is not defined conflict

This topic contains 7 replies, has 3 voices, and was last updated by  Tom 6 months, 2 weeks ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #2754

    drew
    Participant

    I’m noticing a js conflict with Visual Composer (VC) that prevent WPSP’s category and terms dropdowns from working: https://www.screencast.com/t/lbsYY6uw

    VC’s settings panel isn’t recognizing the WPSP post type: https://www.screencast.com/t/cvPjL0oF. that explains the error but I’m not sure what the best way to go about correcting it is, do you have any suggestions?

    This is running at https://adaptistration.com (and even though autoptimize is running, the js module is deactivated so there’s no potential conflict there).

    Many thanks,
    Drew

    #2769

    Tom
    Keymaster

    Hmm, it looks like something need would need to tweak. Their JS should only enqueue if the editor is supported in the post type, as I assume the editor is needed to run VC.

    #2775

    drew
    Participant

    gotcha, is it something I should hang tight on via an impending WPSP update?

    #2778

    nancy
    Participant

    I had this same issue and believe it has something to do with the rights that the user has been assigned. I have not figured out what that is yet, but on duplicated sites, the toggles work when I am signed in as other user types.

    However – an easy fix is to disable Visual Composer temporarily. Then, go in and build your shortcode through the WPShow posts admin. When you are done, re enable VC, enter the shortcode where you like it and then it will work.

    #2781

    drew
    Participant

    Yep, I can confirm disabling VC, setting up and saving the WPSP shortcode post type works.

    #2787

    Tom
    Keymaster

    I’m not sure this is something we can fix in WPSP, as it’s VC enqueuing a script where it shouldn’t. VC itself needs to make sure the current post type being viewed supports the editor. If it doesn’t, VC shouldn’t initiate.

    #2879

    drew
    Participant

    Just a quick follow-up on this. I do hope a solution is available at some point. Did you reach out to WPBakery?

    #2886

    Tom
    Keymaster

    I haven’t – I assumed you already had a line of communication open with them? If they have any questions about the issue, they can contact me here: https://wpshowposts.com/contact/

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

You must be logged in to reply to this topic.