Viewing 26 posts - 1 through 26 (of 26 total)
  • Author
    Posts
  • #1025019

    The WP Crowdfunding plugin is having a problem with the theme. It works fine under the Twenty Seventeen per https://imgur.com/a/ZBTF3U0, but the “Campaign Story” does not appear at http://cautionarycomics.djquad.com/product/ravage-kill-all-men.

    #1025127

    Hey DJQuad,

    Add this to quick css:

    .wpneo-tab-content{
    display:block!important;
    }

    Best regards,
    Jordan Shannon

    #1025634

    That didn’t work.

    #1025721

    Hi,

    Did you add my code to the very top of quick css so it runs first? Also be sure to clear the cache a few times over.

    Best regards,
    Jordan Shannon

    #1025993
    This reply has been marked as private.
    #1026100

    Hi,

    Have you tried disabling all active plugins to see if the issue resolves?

    Best regards,
    Jordan Shannon

    #1026161

    Yes it’s a theme conflict. It works fine with the Twenty Seventeen theme.

    • This reply was modified 6 years, 2 months ago by DJQuad.
    #1026439

    Hi,

    Please provide admin info so we can log in and look into this further.

    Best regards,
    Jordan Shannon

    #1026441

    I provided it above. If you need it again please let me know,

    #1026546

    Hi,
    I took a look at your page and added a image with the media button, I didn’t save it , but you can see it in the the screenshot in Private Content area.

    Best regards,
    Mike

    #1026590

    That’s odd, it doesn’t work for me in Chrome, Firefox, or Edge. Others have reported this as well. And like I said it works fine without the Enfold theme. Any ideas?

    #1026976

    Hi,
    Since I didn’t click save last time I decided to give it another try, and this time save and check the page on the front end. But I was able to add a image to the top & bottom editing sections. Please see the screenshot in Private Content area.
    I then looked at the page with Chrome Dev Tools, and the only warning I got was that TinyMCE had deprecated.

    Deprecated TinyMCE API call: <target>.onNodeChange.add(..)
    wp-tinymce.php?c=1&ver=4800-20180716:11

    But I did notice the backend sidebar seemed to be shaking a little.
    I also tried adding a image to the homepage, and then tested adding images to the product page again with Edge & Firefox. All worked fine.
    Sorry I can’t explain why it’s not working for you, and I can’t think for another way to reproduce the error.
    Please try again in Chrome and when you get the error press the F12 key, I assume your on Windows, and see what errors are listed in the console, and take a screenshot. Here is an example.
    2018-10-26-213926

    Best regards,
    Mike

    #1027175

    I’m not getting any errors when I click on the buttons, it just depresses a bit like normal, but doesn’t do anything. Here’s the console when I load the page though.

    jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1
    [Violation] Forced reflow while executing JavaScript took 30ms
    (index):2152 [Violation] Avoid using document.write().
    (anonymous) @ (index):2152
    crowdfunding-front.js?ver=1.8.6:153 Uncaught TypeError: Cannot read property ‘editor’ of undefined
    at wpneo_upload_image (crowdfunding-front.js?ver=1.8.6:153)
    at HTMLDocument.<anonymous> (crowdfunding-front.js?ver=1.8.6:177)
    at i (jquery.js?ver=1.12.4:2)
    at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4:2)
    at Function.ready (jquery.js?ver=1.12.4:2)
    at HTMLDocument.K (jquery.js?ver=1.12.4:2)
    wpneo_upload_image @ crowdfunding-front.js?ver=1.8.6:153
    (anonymous) @ crowdfunding-front.js?ver=1.8.6:177

    i @ jquery.js?ver=1.12.4:2
    fireWith @ jquery.js?ver=1.12.4:2
    ready @ jquery.js?ver=1.12.4:2
    K @ jquery.js?ver=1.12.4:2

    [Violation] ‘setTimeout’ handler took <N>ms
    [Violation] ‘setTimeout’ handler took <N>ms
    [Violation] ‘setTimeout’ handler took <N>ms
    [Violation] ‘setTimeout’ handler took <N>ms
    [Violation] ‘setTimeout’ handler took <N>ms
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as ‘passive’ to make the page more responsive. See <URL>
    tinymce.min.js?ver=4800-20180716:2 [Violation] Avoid using document.write().
    ux @ tinymce.min.js?ver=4800-20180716:2
    lx @ tinymce.min.js?ver=4800-20180716:2
    vx @ tinymce.min.js?ver=4800-20180716:2
    (anonymous) @ tinymce.min.js?ver=4800-20180716:2
    (anonymous) @ tinymce.min.js?ver=4800-20180716:2
    qt @ tinymce.min.js?ver=4800-20180716:2
    s @ tinymce.min.js?ver=4800-20180716:2
    n @ tinymce.min.js?ver=4800-20180716:2
    u @ tinymce.min.js?ver=4800-20180716:2
    tinymce.min.js?ver=4800-20180716:2 [Violation] Avoid using document.write().
    ux @ tinymce.min.js?ver=4800-20180716:2
    lx @ tinymce.min.js?ver=4800-20180716:2
    vx @ tinymce.min.js?ver=4800-20180716:2
    (anonymous) @ tinymce.min.js?ver=4800-20180716:2
    (anonymous) @ tinymce.min.js?ver=4800-20180716:2
    qt @ tinymce.min.js?ver=4800-20180716:2
    s @ tinymce.min.js?ver=4800-20180716:2
    n @ tinymce.min.js?ver=4800-20180716:2
    u @ tinymce.min.js?ver=4800-20180716:2
    tinymce.min.js?ver=4800-20180716:2 [Violation] ‘load’ handler took 273ms
    [Violation] Forced reflow while executing JavaScript took 65ms
    [Violation] Forced reflow while executing JavaScript took 60ms

    #1028341

    Hi,
    Sorry for the late reply, I’m asking the rest of the team for their thoughts.

    Best regards,
    Mike

    #1029000

    Hi!

    Did you install a multi themes plugin? The page with the campaign form is using a default theme. I would like to disable the plugin so that I can check the issue, but the plugins panel is hidden.

    Regards,
    Ismael

    #1029230

    Sorry, I turned it off.

    #1030229

    Hi,

    Did you install a cache or a copmpression plugin? Please deactivate those temporarily and then add this code in the functions.php file:

    function ava_load_wp_media_files() {
        wp_enqueue_media();
    }
    add_action( 'wp_enqueue_scripts', 'ava_load_wp_media_files' );

    Best regards,
    Ismael

    #1030535

    That didn’t help. I’m not using any cache or compression plugins.

    #1031532

    Hi,

    I’m not really sure what’s causing that. Have you contact the plugin authors? Try to forward the errors to their developers.

    at wpneo_upload_image (crowdfunding-front.js?ver=1.8.6:153)
    at HTMLDocument.<anonymous> (crowdfunding-front.js?ver=1.8.6:177)
    

    Best regards,
    Ismael

    #1032061

    They’re looking into it. Thanks.

    #1032177

    Hi,

    Thanks for the update, please let us know what they have to say about the problem.

    Best regards,
    Rikard

    #1037888

    They’re clueless. I guess I just have to use a plugin like Multiple Themes and use a different theme on those pages. :/

    #1037892

    Also, on http://allcapscomics.sites.djquad.com/shop

    Click the first 2 products. The one created with WP Crowdfunding is very messed up. Do you think that’s another plugin conflict?

    I’m about ready to throw this plugin out the window. Both the plugin and Enfold obviously support Woocommerce which baffles me why there are so many conflicts.

    #1038055

    Hi,
    It is possible that the error is actually something else triggering it, but it looks like you have already tried disabling your other plugins. Please check that Enfold Theme Options > Performance > Load jQuery in your footer is not checked. But other than that it looks like you have already tried everything I can think of.

    Best regards,
    Mike

    #1038312

    It’s not checked. Before I trash this crappy plugin, do you know why the product’s background at http://allcapscomics.sites.djquad.com/product/ethan-van-scivers-cyberfrogbloodhoney-comic-book is blue? Other products like http://allcapscomics.sites.djquad.com/product/12-rules-for-life-an-antidote-to-chaos seem to look fine (barring some CSS tweaks to make it look a little better)

    I believe it just makes a normal Woocommerce product.

    #1038323

    Hi,
    The background color that you are seeing on the page is the background color of your sectors .html, #wrap_all, #main but the reason you have not seen this before is because the sector .container_wrap has the background color of white. So what has happened with the plugin page, is that the .container_wrap has been replaced with .wpneo-wrapper which has no background color in it’s css so the others are showing though.
    This css with easily make the background color white:

    #top #main, .wpneo-wrapper {
    background-color: #fff !important;
    }

    Best regards,
    Mike

Viewing 26 posts - 1 through 26 (of 26 total)
  • You must be logged in to reply to this topic.