Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @weltraumduft,

    Is this error in your Complianz dashboard? I can’t find the console of the browser?

    If so, it might be a false positive and could be gone soon after an automatic recheck by Complianz.

    Let me know!

    regards Aert

    Plugin Contributor Jarno Vos

    (@jarnovos)

    Hi @weltraumduft

    I’m marking this as resolved for now, but feel free to reach out if further assistance is required.

    Kind regards,
    Jarno

    Thread Starter weltraumduft

    (@weltraumduft)

    Hello Jarno, Aert,
    yes it is in the Dashboard.

    Uncaught TypeError: elementorFrontend.elementsHandler is undefined in line 43

    After i install new Update this day, the Error still exist.

    Plugin Contributor Jarno Vos

    (@jarnovos)

    Hi @weltraumduft,

    The error message is only shown in the Dashboard and does not appear anywhere on the front-end of your site, so this shouldn’t really be a cause for concern.

    We show these errors in the back-end because if an error breaks jQuery, Complianz might not run correctly as a result. This error message could help us find the cause of the problem.

    Kind regards,
    Jarno

    Thread Starter weltraumduft

    (@weltraumduft)

    Hello Jarno. The error message shown me in Chrome and Firefox. Today, the error change to another 🙁

    (index):43 Uncaught TypeError: Cannot read property 'runReadyTrigger' of undefined
        at HTMLDocument.cmplz_elementor_fire_initOnReadyComponents ((index):43)
        at HTMLDocument.dispatch (jquery.min.js:2)
        at HTMLDocument.v.handle (jquery.min.js:2)
        at cmplzRunAfterAllScripts (complianz.min.js:1)
        at cmplzEnableMarketing (complianz.min.js:1)
        at setBlockedContentContainer (complianz.min.js:1)
        at conditionally_show_warning (complianz.min.js:1)
        at HTMLDocument.<anonymous> (complianz.min.js:1)
        at e (jquery.min.js:2)
        at t (jquery.min.js:2)

    This error only shown on the start page. and only when i accept all cookies. when i choose ´functionaly cookies only´ the error message gone. When i disable your complianze plugin, the error is gone. Dont know what runReadyTrigger do. It is a function from elementor? Why it is in a complianze fire_initOnReady function?

    I found interesting point: when i disable my youtube video on start page, the error is gone ! I tried to disable the Lazy Load and the private mode. But this is not the solution 🙁 The elementor video box in combination with Complianze makes trouble.

    kind regards, marco

    Thread Starter weltraumduft

    (@weltraumduft)

    sorry I must correct myself!
    We have two different error messages.
    In Firefox “Uncaught TypeError: elementorFrontend.elementsHandler is undefined”
    In Chrome “Uncaught TypeError: Cannot read property ‘runReadyTrigger’ of undefined”

    But… both errors are on line 43 !
    I think it is the same bug, the browser gives different messages.
    I dont talk about Backend, i mean the browser console !

    • This reply was modified 4 years, 6 months ago by weltraumduft.
    Plugin Contributor Jarno Vos

    (@jarnovos)

    Hi @weltraumduft,
    Thank you for the clarification about the error.

    Concerning the error and why it occurs: we have to trigger the “frontend.js” again after un-blocking the video, this works, but it does display a console error. We will contact Elementor and look into this, but without their co-operation, there isn’t really an elegant and permanent solution available.

    We will hide this particular error from the Complianz Dashboard with the coming update, so that at least the +1 disappears.

    Kind regards,
    Jarno

    Thread Starter weltraumduft

    (@weltraumduft)

    Only important is that we have no problem and only a message in console 🙂
    Thanks for your time.

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

The topic ‘Error: elementorFrontend.elementsHandler is undefined’ is closed to new replies.