• Resolved neo2k23

    (@neo2k23)


    I get the following JS messages

    JQMIGRATE: jQuery.fn.bind() is deprecated wp-content/plugins/elementor/assets/lib/tipsy/tipsy.js?ver=1.0.0:180

    QMIGRATE: jQuery.fn.focus() event shorthand is deprecated focusSearch wp-content/plugins/elementor/assets/js/editor.js?ver=3.20.2:36890

    Uncaught TypeError: __webpack_require__.O is not a function.. wp-content/plugins/elementor/assets/js/frontend.js?ver=3.20.2:2803

    Please can you fix these? Thank you

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Joel

    (@joelsm)

    Hi,

    I hope this message finds you in good spirits.

    The errors you’ve reported indicate several issues with the generated package, likely due to misconfiguration or compatibility problems among the various plugins Elementor uses.

    Having reviewed your entire message and the provided screenshots, I suggest the following steps:

    1. Clear Browser Cache: At times, the browser cache might disrupt Elementor’s interface. Please clear your browser cache or access Elementor through an incognito/private window to check if the issue still occurs.
    2. Disable Plugins: It’s possible that other plugins could be conflicting with Elementor. I recommend deactivating other plugins one at a time to see if the issue is resolved. Certain plugins might interfere with Elementor’s functionality.
    3. Switch Theme: As a temporary measure, switch to a default WordPress theme (such as Twenty Twenty-One or Hello Theme) to determine if the problem stems from your current theme.
    4. Update Elementor and WordPress: Ensure you are using the most recent version of Elementor that’s compatible with your WordPress setup. Likewise, update WordPress to its latest version if not already done.
    5. Server Resources: Insufficient server resources can sometimes lead to issues. Please check that your hosting server fulfills Elementor’s minimum requirements for PHP (we recommend version 7.4) and the memory limit.
    6. Reinstall Elementor: Should the above steps not resolve the issue, consider reinstalling Elementor. First, deactivate and delete the current Elementor plugin, then reinstall it from the beginning.

    Always ensure you have a backup of your website before undertaking significant actions, such as deactivating plugins or changing themes, to prevent potential data loss or conflicts.

    If you’re an Elementor Pro user, our pro support is available to you. Please reach out through your My Elementor account, and we’ll strive to resolve this promptly.

    Remember to back up your site before making any major changes. Should you encounter difficulties with any of the suggested steps, please contact your hosting provider for assistance.

    Should you have any more questions or concerns, please don’t hesitate to contact us.

    Best regards,

    Thread Starter neo2k23

    (@neo2k23)

    Hi thanks for the reply, but i just used a clean wp install, installed elementor, activated it, walked through the automatic elementor setup and i got these messages in the new page elementor creates after activating the plugin !

    This has nothing todo with a misconfiguration or cache or setup. The only thing you need to add is two lines of code in your wp-config.php

    define( ‘WP_DEBUG’, true );
    define( ‘SCRIPT_DEBUG’, true );

    That is all. I am just reporting this so you can update your plugin to work flawlessly with jquery 3.7.xx and soon 4.0

    These are deprecated messages caused by the plugin. No elementor pro. Just a clean install.

    Plugin Support aracelil

    (@aracelil)

    .

    • This reply was modified 8 months ago by aracelil.
    • This reply was modified 8 months ago by aracelil.
    Plugin Support aracelil

    (@aracelil)

    Hello. Thanks for the follow up reply.

    Since this is a development based query, please report this issue to our Github account, which is monitored by our developers. Please follow this guide which outlines the steps required to post on our Github: https://github.com/elementor/elementor/blob/master/.github/CONTRIBUTING.md

    We thank you in advance for reporting this issue through the appropriate channel.

    Kind Regards.

    Tim

    (@turrdpress)

    I’m seeing the same issue when SCRIPT_DEBUG is on. When SCRIPT_DEBUG is off, the .min.js version of the script crashes even harder and locks up the editor.

    .O in webpack doesn’t exist. What is .O? Is that another obfuscated object?

    • This reply was modified 5 months, 1 week ago by Tim.
Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.