JavaScript Errors with Jeg Elementor Kit v2.6.8 on Elementor v3.24.x

  • Resolved theodion

    (@theodion)


    1 month, 1 week ago

    After updating to Elementor v3.24.x and Elementor Pro v3.24.x while using Jeg Elementor Kit v2.6.8, we encountered persistent JavaScript errors that break certain elements on the front end. The issue does not occur with Elementor v3.23.0 or earlier versions.

    Additionally, after performing Regenerate CSS & Data and Sync Library, the issue temporarily resolves, but it returns after the second page reload.

    We tested this issue with both the Hello Elementor v3.1.1 and Twenty Twenty-Four themes. All plugins except Elementor, Elementor Pro, and Jeg Elementor Kit were deactivated during the tests, and the issue persists. The following errors consistently appear in the browser’s console:

    Uncaught TypeError: Cannot read properties of undefined (reading 'handlers')
    at Object. (sticky-element.js?ver=2.6.8:1:969)
    at i (sticky-element.js?ver=2.6.8:1:110)
    at sticky-element.js?ver=2.6.8:1:902
    at sticky-element.js?ver=2.6.8:1:911

    Uncaught TypeError: Cannot read properties of undefined (reading 'handlers')
    at 820 (frontend.min.js?ver=3.24.1:2:4477)
    at webpack_require (webpack-pro.runtime.min.js?ver=3.24.1:2:150)
    at 4906 (frontend.min.js?ver=3.24.1:2:4134)
    at webpack_require (webpack-pro.runtime.min.js?ver=3.24.1:2:150)
    at 3000 (frontend.min.js?ver=3.24.1:2:139)
    at webpack_require (webpack-pro.runtime.min.js?ver=3.24.1:2:150)
    at frontend.min.js?ver=3.24.1:2:24995
    at webpackJsonpCallback (webpack-pro.runtime.min.js?ver=3.24.1:2:5854)
    at frontend.min.js?ver=3.24.1:2:69

    Uncaught TypeError: Cannot read properties of undefined (reading 'tools')
    at Frontend.initOnReadyComponents (https://padelpro.cy/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.24.1:2:7393)
    at Frontend.init (https://padelpro.cy/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.24.1:2:9297)
    at HTMLDocument. (https://padelpro.cy/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.24.1:2:9523)
    at e (https://padelpro.cy/wp-includes/js/jquery/jquery.min.js?ver=3.7.1:2:27028)
    at https://padelpro.cy/wp-includes/js/jquery/jquery.min.js?ver=3.7.1:2:27330


    We also tested:

    • Deactivating all plugins except Elementor, Elementor Pro, and Jeg Elementor Kit.
    • Switching to default themes like Hello Elementor v3.1.1 and Twenty Twenty-Four.
    • Deactivating caches.

    Downgrading Elementor and Elementor Pro to v3.23.0 resolved the issue, indicating the conflict lies between Jeg Elementor Kit and Elementor v3.24.x.

    Please advise if there is a fix or update to resolve this issue. Thank you!

    • This topic was modified 1 month, 1 week ago by theodion.

    The page I need help with: [log in to see the link]

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

  • Same errors here!

    Plugin Author Fauzan Jegstudio

    (@fauzanjegstudio)

    Hello @theodion & @markk26,

    We sincerely apologize for the delay in our response and for any inconvenience you have experienced. The issue is caused by an update to the JavaScript registration mechanism in Elementor since version 3.24.0.

    We have already updated the Jeg Elementor Kit to version 2.6.9, which includes a fix for this issue. We recommend updating the Jeg Elementor Kit plugin to resolve the problem.

    We look forward to hearing back from you.

    Thank You

    Thread Starter theodion

    (@theodion)

    Thank you. I can confirm that the issue has been resolved.

    gekstrom

    (@gekstrom)

    @fauzanjegstudio I’m a developer creating custom widget add-ons as well. I’m experiencing the exact same issue and not having any luck finding a fix for my plugins. Would you mind letting me know how you fixed the issue in your plugin? Any insight would be greatly appreciated!

    Plugin Author Fauzan Jegstudio

    (@fauzanjegstudio)

    Hello @theodion,

    You’re welcome! Thank you for getting back to us, we’re glad to hear that! ??

    If you enjoy using our plugin, please don’t forget to leave us feedback by rating the Jeg Elementor Kit plugin.

    Thank you!

    Plugin Author Fauzan Jegstudio

    (@fauzanjegstudio)

    Hello @gekstrom,

    Could you please share with us how you are registering your scripts (JavaScript)?

    If you are currently using the action hook elementor/frontend/after_register_scripts to register scripts, try replacing this action hook with wp_enqueue_scripts which is the default in WordPress.

    Screenshot-2024-09-18-at-10-04-21

    We hope this solution helps.

    Thank You!

    nuurhasan

    (@nuurhasan)

    Hi, facing similar issue here. Website loading fine in Elementor edit mode but on front-end it appears disoriented.

    • I have regenerated CSS files
    • Cleared caches
    • Deactivated Element caching
    • Increased memory limit to 512M

    All these doesn’t seem to work.

    gekstrom

    (@gekstrom)

    @fauzanjegstudio your a lifesaver! That did the trick. Thank you!!!

    Plugin Author Fauzan Jegstudio

    (@fauzanjegstudio)

    Hello @nuurhasan,

    We sincerely apologize for the delay in responding. Thank you as well for outlining the steps you have taken so far.

    The topic of discussion in this forum is related to the Elementor update that conflicts with the Jeg Elementor Kit. Have you tried updating the Jeg Elementor Kit to version 2.6.9?

    If the issue persists after updating the Jeg Elementor Kit, we assume that the problem you’re experiencing might be different. Could you kindly create a new topic and provide the URL for your site? This will allow us to look closer and better understand the situation.

    We look forward to your response.

    Thank You

    Plugin Author Fauzan Jegstudio

    (@fauzanjegstudio)

    You’re welcome @gekstrom!

    We’re glad to hear that ??

    Have a great weekend! ???

    You are all amazing. Thank you! We fixed this exact same issue with this approch. Many thanks

    Plugin Author Fauzan Jegstudio

    (@fauzanjegstudio)

    You’re welcome @frymo!

    We’re glad to know this was helpful ??

    If you encounter any other issues, please don’t hesitate to create a new topic!

    Thank You

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