Home Forums WoodMart – Premium Template AJAX Add to cart not compatible with Yith Product addons Premium

This topic contains 11 replies, has 3 voices, and was last updated by Artem Temos Artem Temos 1 week, 1 day ago.

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #126520

    lukepedroni
    Customer

    After the last theme update, we found out that the theme add to cart ajax function is not compatible with yith product addons.

    The addons price is not added to the product price.

    #126528

    Hi,

    Try to add the following PHP code snippet to the child theme functions.php file to fix this http://prntscr.com/nr8vh5

    wp_enqueue_script( 'woodmart-waypoint', 'https://cdnjs.cloudflare.com/ajax/libs/waypoints/2.0.2/waypoints.min.js', array( 'jquery' ), woodmart_get_theme_info( 'Version' ), true );

    We shall fix it in our nearest update.

    Regards

    #126529

    lukepedroni
    Customer

    And if we do not use a child theme?

    #126549

    Hello,

    Please upload and install it. In the nearest update we shall fix this issue and you will remove the child theme and switch to the parent.

    Best Regards

    #127761

    lukepedroni
    Customer

    We upgrade to V 3.8, but the issue wasn’t fixed. Still the addon price is not added to the product price.

    #127779

    Hi,

    Could you please send us a link to your website where we can see this issue?

    Kind Regards

    #128040

    lukepedroni
    Customer

    Sure, see the private content.

    Private Content Hidden
    #128046

    This plugin adds additional fields and that is why the AJAX add to cart will not work with it. You need to disable this function.

    #128047

    lukepedroni
    Customer

    Why has it worked for the previous year?

    #128049

    This custom function never worked with any plugins that add additional fields to the add to cart form. It is also mentioned in this option’s description.

    #128084

    lukepedroni
    Customer

    I’m sorry I have to contradict you, because it worked up to version 3.7 of your template. It has worked perfectly since 1.7.2018

    #128117

    In this case, try to install a previous version and send us a link where we can check this.

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

You must be logged in to reply to this topic.