Conflict with Elementor Pro in 2.2.0 (Fatal Error

  • Resolved Jorgu5

    (@internetoholik)


    3 years, 7 months ago

    Hey,

    Getting these error when updated to the newest 2.2.0 version ->

    Uncaught Error: Call to a member function get_component() on null in /nas/content/live/uxmagazine/wp-content/plugins/elementor-pro/modules/global-widget/widgets/global-widget.php:180\nStack trace:\n#0 /nas/content/live/uxmagazine/wp-content/plugins/elementor-pro/modules/global-widget/widgets/global-widget.php(68): ElementorPro\\Modules\\GlobalWidget\\Widgets\\Global_Widget->set_preview_settings(Array)\n#1 /nas/content/live/uxmagazine/wp-content/plugins/shortpixel-adaptive-images/includes/controllers/short-pixel-ai.class.php(358): ElementorPro\\Modules\\GlobalWidget\\Widgets\\Global_Widget->get_raw_data()\n#2 /nas/content/live/uxmagazine/wp-includes/class-wp-hook.php(292): ShortPixelAI->parse_elementor_css(Object(Elementor\\Core\\DynamicTags\\Dynamic_CSS), Object(ElementorPro\\Modules\\GlobalWidget\\Widgets\\Global_Widget))\n#3 /nas/content/live/uxmagazine/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)\n#4 /nas/content/live/uxmagazine/wp-includes/plugin.php(484): WP_Hook->do_action(Array)\n#5 /nas/content/l in /nas/content/live/uxmagazine/wp-content/plugins/elementor-pro/modules/global-widget/widgets/global-widget.php on line 180, referer: https://uxmagazine.wpengine.com/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Gerard Blanco

    (@sixaxis)

    Thanks @internetoholik for reporting this!

    Could you please go to Tools > Site Health > Info, click on “Copy site info to clipboard” and paste it here?

    Thank you!

    Plugin Author Pedro

    (@petredobrescu)

    Hello again @internetoholik and thanks for reporting this!

    Unfortunately, this seems to be a bug in Elementor Pro, that we have previously tried to report to the Elementor team, but because we don’t have a Pro license, we didn’t really manage to progress.

    Until version 2.2.0, we had a work-around for this type of error, where we were simply excluding from processing the situations where this error would arise. However, this was bringing a bigger downside – images not being properly processed in more cases than the ones where errors were thrown. So we decided to remove the work-around and hopefully we’ll be able to get to the bottom of this error.

    As a conclusion: please start a support thread with the Elementor Pro team about this, where it would be perfect if you could include our support e-mail as well – [email protected] – and I’ll be very happy to follow up on that thread in order to see if there’s anything from our end that needs to be changed in the integration we have with Elementor.

    Many thanks,
    Pedro

    @petredobrescu : Neev from Elementor Pro Support answered me and I found the time now (8.5.2021) to do a screencast for him where I explain the problem once again. I’ve also sent Neev your E-Mail from above and told him that he should get in direct contact with you, because it’s not just a problem with my website.

    Let’s hope that the Elementor Pro team will soon find a solution, so that we can use Shortpixel Ai again.

    Plugin Author Pedro

    (@petredobrescu)

    Thanks, @agneskarikaturen!

    I’m also in touch with Anatolii from the Tier 3 support of Elementor and I was assured that the case was passed on to the development team. I haven’t heard back from them yet, but hopefully they’ll have a fix soon.

    Thanks for following this up!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Conflict with Elementor Pro in 2.2.0 (Fatal Error’ is closed to new replies.