Conflict with Elementor

  • Resolved supervinnie41

    (@supervinnie41)


    3 weeks ago

    Hello,

    I’ve just updated my Elementor Plugins, including a few others. But there seems to be going something wrong between your plugin and Elementor. I use Elementor and Elementor Pro. And as long as MC4WP is activated, I can’t open the editor. Once I disable MC4WP everything works perfectly fine again.
    Other plugins don’t seem to affect Elementor at all, its only the MC4WP plugin.

    These are the plugins I am using. Everything, including WordPress itself is updated at least once a week (just did all the updates for this week)



    Phlox Core Elements
    Phlox Portfolio
    Akismet Anti-spam: Spam Protection
    All-in-One WP Migration
    Calculated Fields Form Professional
    Classic Editor
    Classic Widgets
    Contact Form 7
    Deliverability
    Depicter
    Elementor Pro
    Elementor
    E-Mail Log
    Font Awesome
    GTranslate
    Health Check & Troubleshooting
    IndexNow
    Jetpack
    MC4WP: Mailchimp for WordPress
    Media Library Folders
    NinjaScanner
    Ocean Extra
    Popup Maker
    Shortcode in Menus
    Yoast SEO
    WP Consent API
    WP Mail SMTP
    Widgets for Google Reviews
    Smush
    WP ULike
    Social Chat

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hey @supervinnie41,

    Thanks for reaching out to us.

    Can you please test if disabling “Elementor Pro” and see if the issue persists? If yes, then we can try replicating it with the free version of Elementor.

    Thread Starter supervinnie41

    (@supervinnie41)

    Hi Harish,

    I owe you an apology. To get the answer to your question I did some more testing and, even though MC4WP was already disabled, I suddenly got the same error again.

    After more research we discovered that there is a Elementor-addon that causes the problem. It seems to conflict with MC4WP (if active) but also conflicts with another basic Elementor element. We did some more tests on a website that never had MC4WP, and we could repeat the problem there.

    So my apologies. It seems we might have been to quick in thinking that your plugin was the problem.

    Plugin Contributor Lap

    (@lapzor)

    Thanks for the update!

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