Home Forums WoodMart support forum JavaScript conflict between WoodMart theme and Elementor Pro

JavaScript conflict between WoodMart theme and Elementor Pro

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #724991

    vargha.bahagir
    Participant

    Hello,

    I am using the WoodMart theme on my website and I am facing a serious JavaScript conflict after activating Elementor
    The issue:
    When Elementor Pro is disabled, the website works normally and all WoodMart JavaScript features are working correctly.
    But when I activate Elementor Pro, several WoodMart JS functionalities stop working completely. The theme JavaScript seems to break.
    Affected areas include WoodMart frontend scripts (menus, dynamic elements, theme interactions, etc.).
    I checked the browser console and the only visible warning is:
    Source map error: request failed with status 404

    Source Map URL:
    swiper-bundle.min.js.map
    I understand this source map warning may not be the main cause, but it appears after Elementor activation.
    Troubleshooting already done:
    Disabled all cache/performance plugins (no LiteSpeed Cache, WP Rocket, Autoptimize, etc.)
    Tested with only Elementor, Elementor Pro, WooCommerce, WoodMart Core active
    Regenerated Elementor CSS & Data
    Cleared website/browser cache
    Checked Elementor features and performance settings
    The conflict happens only when Elementor Pro is active.

    Could you please check this issue and let me know:
    Which WoodMart script is conflicting with Elementor Pro?
    Is there any compatibility issue with the current WoodMart version and Elementor Pro?
    Is there any recommended fix or configuration for WoodMart + Elementor Pro?

    Thanks,
    Vargha

    #725010

    Serg Sokhatskyi
    Keymaster
    Xtemos team

    Hi there,
    Thanks for reaching out.

    We checked your site but couldn’t find any errors or broken functionality on the front end. Could you please share screenshots or, ideally, a short screen recording that clearly shows the issue when Elementor Pro is activated? This will help us understand how to reproduce the problem on our side.
    Also, allow us to turn off external plugins on your website so we can isolate the problem

    Kind regards,
    XTemos Studio

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