TypeError: i.useDispatch(…) is null

  • Resolved hejhog

    (@hejhog)


    9 months ago

    The following links below all result in the error TypeError: i.useDispatch(…) is null
    Woocomerce > Customers
    Woocommerce > Extensions
    Analytics > All menu links

    I have tried:
    Status > Tools > Woocommerce Clear Transients
    Status > Tools > WordPress Clear Transients
    Status > Tools > Update Database
    Status > Tools > Verify Database Tables
    Status > Tools > Clear Woocommerce Cache
    Status > Tools > Clear Analytics Cache
    Restarting the Server
    Disabling all plugins (apart from Woocomerce and PayPal)

    This error has developed in the last 1-5 days. Any suggestions?


    WordPress Environment

    WordPress address (URL): https://runningharedesigns.co.uk
    Site address (URL): https://runningharedesigns.co.uk
    WC Version: 10.1.2
    Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.
    Action Scheduler Version: ✔ 3.9.3
    Log Directory Writable: ✔
    WP Version: 6.8.2
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode: –
    WP Cron: –
    Language: en_GB
    External object cache: ✔ Server Environment

    Server Info: Apache
    Server Architecture: Linux 6.8.0-79-generic x86_64
    PHP Version: 8.3.25
    PHP Post Max Size: 128 MB
    PHP Time Limit: 30
    PHP Max Input Vars: 1000
    cURL Version: 8.5.0
    OpenSSL/3.0.13

    SUHOSIN Installed: –
    MySQL Version: 10.11.13-MariaDB-0ubuntu0.24.04.1
    Max Upload Size: 128 MB
    Default Timezone is UTC: ✔
    fsockopen/cURL: ✔
    SoapClient: ✔
    DOMDocument: ✔
    GZip: ✔
    Multibyte String: ✔
    Remote Post: ✔
    Remote Get: ✔

    ### Active Plugins (11) ###

    Admin Menu Editor: by Janis Elsts – 1.14.1
    Code Snippets: by Code Snippets Pro – 3.7.0
    GTG Product Feed for Shopping: by WPOPAL – 1.3.0
    XML Sitemap Generator for Google: by Auctollo – 4.1.21
    Insert PHP Code Snippet: by xyzscripts.com – 1.4.3
    Real Media Library (Free): by devowl.io – 4.22.54
    Redis Object Cache: by Till Krüss – 2.6.5
    WooCommerce PayPal Payments: by PayPal – 3.1.0
    WooCommerce: by Automattic – 10.1.2
    WPForms Lite: by WPForms – 1.9.7.3
    Smart Coupons For WooCommerce Coupons: by WebToffee – 2.2.3

Viewing 3 replies - 1 through 3 (of 3 total)
  • LovingBro (woo-hc)

    (@lovingbro)

    9 months ago

    Hi @hejhog,

    I understand how disruptive it is when key WooCommerce admin screens throw a TypeError like i.useDispatch(…) is null, especially since it affects Customers, Extensions, and Analytics. You’ve already been very thorough with your troubleshooting steps, which helps narrow things down.

    From the details you shared, this error often points to a JavaScript conflict in the WooCommerce Admin package. It can happen after recent updates, sometimes in combination with object caching or plugin conflicts. Let’s try these next steps:

    1. Temporarily disable object caching — since you’re using Redis Object Cache, try turning it off and then reloading the affected admin pages. This will help rule out stale cached assets causing the error.
    2. Check for browser console errors — you already saw the TypeError, but could you also open your browser’s developer console, refresh the page, and share a screenshot of all the red error messages via https://snipboard.io? That will confirm if it’s limited to WooCommerce scripts or something broader.
    3. Reinstall WooCommerce Admin assets — even though WooCommerce is active, sometimes the JavaScript assets get corrupted. You can delete and reinstall the WooCommerce plugin from Plugins → Add New, without losing your data.
    4. Conflict confirmation — you’ve disabled other plugins, which is great, but did you also try switching to a default theme like Storefront or Twenty Twenty-Four? That can confirm if the issue is theme-related.
    5. System Status Report — please share your full WooCommerce System Status Report through https://pastebin.com or https://gist.github.com so we can review environment details more closely.

    Once we rule out caching and asset corruption, we’ll have a clearer picture of whether this is a local conflict or something that needs escalation.

    Feel free to let us know how it goes.

    Thread Starter hejhog

    (@hejhog)

    9 months ago

    You’re a star. Number 2 got me thinking. I was seeing the issue across multiple devices therefore it did not occur to me it was a browser issue. However, all devices run Firefox with the same set of extensions….

    Running Firefox in safe mode cured the issue therefore an updated Firefox extension is to blame.

    In the future I will ALWAYS CHECK THE BROWSER FIRST!!!!!

    LovingBro (woo-hc)

    (@lovingbro)

    9 months ago

    Hi @hejhog,

    That’s fantastic to hear! I’m glad you tracked it down to the browser extensions in Firefox, it’s easy to overlook when the issue appears across multiple devices. Your note is a great reminder that browser-level conflicts can mimic site-side problems.

    Thanks for sharing your findings as well, it will surely help others facing a similar issue. If WooCommerce has been useful for your store and you’re happy with the support received, we’d truly appreciate it if you could leave us a quick 5-star review here: https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/#new-post

    Feel free to open a new forum topic if you run into any other problem.

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

The topic ‘TypeError: i.useDispatch(…) is null’ is closed to new replies.