• On a client side the current version of Grow for WP (disabling the conflict allowed Elementor to load again) conflicts with the latest version of Elementor (and Pro)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @cousett,

    Thanks for reaching out! We’ve seen a few others report this, and while it looks like the issue stems from Elementor’s side, we’re both working on a resolution for the issue that prevents a user from properly accessing the Elementor editor while Grow for WP is active.

    In the meantime, you should be able to work around this by manually adding your Grow script to your site, and then you can disable the Grow for WP plugin. That should keep Grow up and running, while bypassing the current conflict.

    Let us know if this doesn’t work for you, and we can take another look.

    Following this topic as a client of mine has the issue. Elementor loads in FireFox, but in Chrome it only loads if Grow for WP is disabled.

    The problem is still here, for anyone setting up the grow by mediavine and getting error message saying that existing ads from previous network are still there, despite removing all codes, the problem is in conflict with elementor.

    Once I changed theme to default one, I have managed to setup grow through plugin and following steps, but this is not the permanent solution.

    People need to know that Elementor and Grow are not compatible for some reason.

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