Frontend JS Error After Upgrade to 3.21.2-3.21.3 in Admin Mode

  • Resolved HarshS

    (@harshs)


    5 months, 4 weeks ago

    After upgrading Elementor to 3.21.2, the following frontend js error started occuring while editing pages in Admin mode. It did not fix even after upgrading to the next 3.21.3 version. It’s not though preventing to edit the pages but definitely slowing the page load down.

    frontend.min.js?ver=3.21.3:2 Uncaught TypeError: e.O is not a function
    at frontend.min.js?ver=3.21.3:2:39876
    at webpackJsonpCallback (styleguide-app-initiator.min.js?ver=3.21.3:3:13486)
    at webpackJsonpCallback (webpack.runtime.min.js?ver=3.21.3:2:4680)
    at frontend.min.js?ver=3.21.3:2:74

    Suggest any fix for this. Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)

  • I have the same issue, you fix that?

    I have the same issue. My system logged below:

    JS: showing 2 of 2JS: 2024-04-27 17:07:54 [error X 1][https://*****/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.21.3:2:30429] elementor.settings.page is undefined
    JS: 2024-04-27 17:36:03 [error X 1][https://****/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.21.3:3:1142667] Element type not found: ‘ct_title’

    Plugin Support Elementor Team

    (@ricav)

    Hi @harshs,

    Please make sure that the DEBUG mode is inactive on your website.

    ?In your wp-config.php file search for following line:
    define(‘WP_DEBUG’, true);

    And replace it with:
    define(‘WP_DEBUG’, false);

    If you are unfamiliar with the site’s wp-config.php file, you can reach out to your hosting provider for assistance.

    If the issue persists, please provide us with the screenshots showing the whole page with the error and the website URL so we can further investigate.

    I hope that helps.

    Kind regards,

    Thread Starter HarshS

    (@harshs)

    Hi @ricav,

    I have checked and found that the WP_DEBUG flag is already set to FALSE. However, it made me curious why should this error be dependent on the error flag? There could be many instances when we need to turn on the debugging, so will this error always come in those cases. There should be a cleaner way to handle the frontend JS error.

    Thanks.

    Plugin Support aracelil

    (@aracelil)

    Hi, @harshs.

    Thank you for reaching out to us. Our developers are aware of this error and it has been documented internally on our end. It should not affect Elementor overall and the user experience.?

    If you wish, you can also contribute to the following thread on our Github page for this issue: https://github.com/elementor/elementor/issues/26121.

    While I can’t provide an ETA for a resolution at this time, I invite you to keep an eye on our changelogs, where our developers share updates:

    Elementor Changelog?

    Elementor Pro Changelog?

    Kind Regards.

    Thread Starter HarshS

    (@harshs)

    Thanks. I think it’s alright you accepted the issue though it is definitely not that critical. Still, I hope it gets resolved. Just ending with a positive note – I observed Elementor is getting better, definitely far better than the last years updates.

    Same issue.. prevents some image assets (including main site image) from being loaded in Edit mode with Elementor Pro.

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