Viewing 17 posts - 1 through 17 (of 17 total)
  • Author
    Posts
  • #410758

    hi – using woocommerce on a client site, having an issue with one of their plugins (custom checkout fields). i asked them for help – they have identified a javascript error coming from enfold. they asked me to contact you.

    from woo:

    There appears to be a JavaScript error occurring on that page caused by the Enfold theme. See http://cld.wthms.co/BWxa . kriesi.at is typically very good about their updates and support on issues like this. Are there any updates available for your theme? If not, would you mind reaching out to them on this issue to see if they are aware of it?

    let me know if you need login info for my client site to investigate. thanks for looking into this.

    #411257

    Hey charger70!

    So it’s a Woocommerce extension your using? Go ahead and send us a WordPress login and we’ll take a look.

    Cheers!
    Elliott

    • This reply was modified 9 years, 9 months ago by Elliott.
    #411263
    This reply has been marked as private.
    #411266

    the issue began relatively recently, i believe after an update to Enfold. according to the woo people, from the message above, they believe it’s a JS error coming from Enfold, a minor one but enough to keep the plugin from working properly.

    thanks for looking into it. i really appreciate it.

    #411794

    Hi!

    please try to deactivate all other plugins, to see if one might cause this issue. However Kriesi will release an update soon ( I think tomorrow), which will fix it I think.

    Regards,
    Andy

    #412287

    hi Andy – we’ve already done this with the support team at WooCommerce. that’s when they identified the error as coming from the Enfold theme, which is why i brought it to you all. glad to hear there will be a theme fix for this soon. i appreciate everything Kriesi does to keep Enfold the best it can be! i use it everywhere!

    #412794

    Hi!

    Where does this error comes up?

    Best regards,
    Josue

    #412795

    josue: in the backend, when you go to add a new field or even modify existing fields. it’s like it’s locked – i can’t do anything with it anymore. i installed the new Enfold update but no change, as Andy thought might be the case.

    #412829

    Hi!

    Do you mean when editing a Product right? try adding this to your wp-config.php file:

    define( 'CONCATENATE_SCRIPTS', false );
    

    Best regards,
    Josue

    #413150

    no change, josue. very frustrating. thanks for your help.

    #413301

    I’m discarding WC extensions and i think the one that causes the conflict is actually WooCommerce Smart Coupons, it’s disabled now, please confirm if the error is still coming up on your end.

    #413364

    It may be fixed in the next version of the plugin:
    http://dzv365zjfbd8v.cloudfront.net/changelogs/woocommerce-smart-coupons/changelog.txt

    #413374

    i updated, still the same issue. i am unable to update the Checkout Fields Editor to the new version (1.3.0) from the current (1.2.11). i have asked Pagely (the hosting company) to look into it, and i’ve also asked Woo to look into it. I’ll keep you posted, Josue. thank you for your help. much appreciated.

    #413393

    Sure, let us know what they say.

    Regards,
    Josue

    #414781

    Further info from Woo:

    Hi Jim,

    The issue is definitely theme related as the theme is using chosen which is what Checkout Field Editor is also attempting to use. See http://cld.wthms.co/JYYZ. Switching to a default theme such as Twenty Fifteen would solve this for example.

    I’m not sure how we could proceed here. Is there anything the Enfold developers can provide to disable or remove chosen for that page? Checkout Field Editor needs it for that page.

    So their analysis shows that the Enfold theme and the Checkout Fields Editor plugin are conflicting over this chosen command. What can we do?

    #414801

    Hey!

    I activated Twenty Fourteen, went to the Checkout Fields page and the error still appeared – http://a.pomf.se/ouzlhf.png (note there is no “Enfold” menu item at the left).

    Best regards,
    Josue

    #414977

    well, i think we’ve figured it out, josue; it was a plugin conflict with one minor element of one plugin: ignitewoo’s automatic cart discount. deactivated, and all better. thanks again for all your help. you were huge, sticking in there with us. very much appreciated!

Viewing 17 posts - 1 through 17 (of 17 total)
  • The topic ‘Javascript Error in Backend According to Woo’ is closed to new replies.