• Hello WooCommerce Support,

    I need help resolving a persistent JavaScript error on my website, https://burrostruccante.com.

    The problem started while I was configuring WooPayments and PayPal and testing the payment functionality.

    The WooCommerce Admin Home page crashes and displays:

    TypeError: n[e] is not a function

    The Payments dashboard has also displayed:

    TypeError: Cannot read properties of undefined (reading 'call')

    Troubleshooting already performed:

    • Disabled WooCommerce PayPal Payments.
    • Disabled WooPayments.
    • Disabled payment test mode.
    • Restored a previous website backup.
    • Checked WooCommerce logs for fatal errors.
    • Tested the website using WordPress troubleshooting mode.

    Unfortunately, the problem persists even when the payment plugins are disabled.

    WordPress version: 7.1.3.

    The website is hosted by Register.it and is not yet publicly launched.

    Could you please help me identify whether this is a WooCommerce Admin JavaScript issue, a plugin conflict, or a problem with the installation?

    Please let me know which additional diagnostic information you need.

    Thank you for your assistance.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi sonian73, since the crash persists with both payment plugins disabled, I wouldn’t repeat that step or assume either plugin is the cause. The short minified errors alone don’t identify the failing component.

    Could you share your WooCommerce version and the first error’s full expanded console stack, including the script filename and line number? Open the browser’s developer tools, select Console, then reload the affected Admin Home page. The WordPress guide explains how to capture this: https://developer.wordpress.org/advanced-administration/debug/debug-javascript/

    Also, in the troubleshooting-mode test you already ran, was WooCommerce the only active plugin with a default theme, and did the same Admin Home error occur in that combination? That detail will help distinguish the test from just disabling the payment plugins.

    Before posting the stack, remove any tokens, customer information or other private data. No login details are needed. This is a diagnostic next step, not a confirmed fix.

    Thread Starter sonian73

    (@sonian73)

    Hello,

    Thank you for your response.

    My WooCommerce version is 11.2.1.

    The error is:
    TypeError: n[e] is not a function

    The stack trace points to:
    wp-content/plugins/woocommerce/assets/client/admin/app/index.js

    The error persists even when WooPayments and WooCommerce PayPal Payments are disabled.

    I previously used Health Check troubleshooting mode, but I cannot confirm whether WooCommerce was the only active plugin with a default theme during that test.

    I will provide the complete console error details.

    Thank you.

    That n[e] is not a function error usually means mismatched cached admin JavaScript chunks. Clear any server or CDN cache for /wp-content/plugins/woocommerce/assets/, then go to WooCommerce › Status › Tools and clear the transients. Also check the browser console’s Network tab for a 404 or HTML response on a .js file; Register.it’s caching or a security rule may be serving the wrong file.

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

You must be logged in to reply to this topic.