• Hi there. I found an issue. I use elementor.
    But If I activate your plugin it generates a console alert with the error
    "Uncaught TypeError: elementor.settings[e] is undefined" with lines like this in console:

    initEditorListeners https://[MY HIDDEN URL]/wp-content/plugins/elementor/assets/js/frontend-modules.min.js:2
    initEditorListeners https://[MY HIDDEN URL]/wp-content/plugins/elementor/assets/js/frontend-modules.min.js:2
    getEditorListeners https://[MY HIDDEN URL]/wp-content/plugins/elementor/assets/js/frontend-modules.min.js:2
    addEditorListeners https://[MY HIDDEN URL]/wp-content/plugins/elementor/assets/js/frontend-modules.min.js:2
    __construct https://[MY HIDDEN URL]/wp-content/plugins/elementor/assets/js/frontend-modules.min.js:2

    And so on…

    If I disable your plugin all works normally and smooth. Sometimes it even block elementor to load page and work normally.

    • This topic was modified 4 years, 3 months ago by masterbip.
    • This topic was modified 4 years, 3 months ago by masterbip.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Hey there! Sorry you’re having issues. I’ll need to test with elementor. Could you help me better identify where this error is showing up? Are you seeing these console errors on a specific admin page or on the front end of your site?

    Thread Starter masterbip

    (@masterbip)

    Hi there Joshua. That was fast!
    Ok… When you edit any content with Elementor (let’s say a page) you will get all those errors in console.
    So it is not in the admin or front end but when editing a page with Elementor.

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Ah, ok. I’ll see if I can get replicate the issue with the free version, though it might be a week or two before I have a fix figured out.

    Plugin Author Joshua David Nelson

    (@joshuadnelson)

    Hey there, I have tested this and my experience with Elementor so far is that the plugin itself does not play well with the new block editor. Switching back and forth causes all sorts of console errors and block issues (without Disable Blog active).

    With Disable Blog activated I wasn’t able to replicate those specific errors you mention. They appear to be related to the Elementor plugin settings, so perhaps it is something specific to your setup.

    Beyond that you would need to reach out to the Elementor support for further help. If they are able to identify something specific that is being impacted by Disable Blog I’d be happy to find a fix, but I can’t feasibly debug the Elementor plugin itself.

    I have been working on Disable Blog version 0.4.9 and have it nearly ready to go. Once that’s available, it might resolve your issue. If you are eager and able to test this in a test site (do not test in-development code on a live/production site), you could try using the develop branch on the Github repository to see if your issues are resolved with the new version.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Issue with latest Elementor’ is closed to new replies.