Elementor, plugin conflict

  • Resolved skinner009

    (@skinner009)


    6 years, 4 months ago

    Hi, this is an FYI, I exchanged email with Elementor and they said you needed to address it — When both Elementor and your plugin are activated, the Elementor editing plugin refuses to load internal pages, spitting out a 500 error. The front page editing works fine for some reason.

    I think they are having challenges. Prior to their latest update, when both plugins were running, the front page would not edit, but only froze up, spitting out a fatal memory error, and all internal pages edited fine. Now, after their update, the 500s keep coming back.

    Again, this is only when both are running. I can easily turn them both on and run the site, it doesn’t affect the front end, just their editing platform. Thanks for your cool work, have a good week.

Viewing 1 replies (of 1 total)
  • Phil

    (@fullysupportedphil)

    Automattic Happiness Engineer

    Hey @skinner009,

    Thanks for the heads up. We don’t typically adjust our plugins to work around incompatibilities caused by third-party plugins. As the adjustments needed may break functionality for other users not using the same third-party plugins. That being said, I’ll pass this along to our dev team just in case ??

    We follow the standard coding practices for WordPress and WooCommerce, so I’m not sure what the Elementor devs are doing that is causing the conflict. As I mentioned while we don’t code our plugins around third-party plugins, there are a large number of page builder plugins that work normally with both WooCommerce and our Stripe plugin, so hopefully their team can correct the issue it’s causing in one of their updates.

    Thanks again for the heads up and enjoy the rest of your week!

Viewing 1 replies (of 1 total)
  • The topic ‘Elementor, plugin conflict’ is closed to new replies.