Hi. I cannot setup WooCommerce using the setup wizard. If I browse to the ‘Setup Wizard’ page, I get “Cannot read properties of undefined (reading ‘title’)” in the console log.
Does anyone have any ideas? Perhaps someone can tell me what data it is missing exactly in ‘title’ and where I can make sure a title exists so I can get around this bug for now until the developers release a proper fix.
Yes, I have tried disabling my plugins and reverting back to the default WordPress 2025 theme. Same issue happens. Nothing in the PHP logs as well. I genuinely feel this is a bug in the latest build of WooCommerce. As a note, I’m using WordPress 6.9 with PHP 8.2.5.
Please don’t ask for access to my site. I have tried a fresh install and the same issue happens.
Thanks.
The page I need help with: [log in to see the link]
Thank you for reaching out and for explaining the issue you’re experiencing. I understand how frustrating and confusing situations like this can be, especially when you’re trying to set up WooCommerce quickly.
To better understand what’s happening, could you clarify what exactly occurs when you try to complete the setup wizard? Aside from the console error, are you stuck in a loop, seeing an error message, or does the setup wizard page fail to load?
When you reply, please record a short Loom video showing your screen as you attempt to complete the setup wizard. This will help us see exactly what happens on your end.
Could you please share your system status report by going to WooCommerce > Status > Get report > Copy for support, and then paste it on Pastebin? This type of error often occurs because of caching problems or conflicts with browser extensions or other plugins.
In the meantime, try clearing both your site cache and your browser cache, then run the setup wizard again to see if anything changes. I’ll be waiting for your system status report and update with clearing the cache before we proceed with any conflict test.
Seeming as you have had two people report this issue within 4 weeks of each other on new, clean installs – I’d say to test that it’s working on your end. Please confirm back to me whether or not you could successfully get the setup wizard to continue to load.
Thanks for your follow-up. I’ve tested this on my own clean setup, and the setup wizard is loading and working correctly on my end. I understand your concern since a couple of users have reported similar issues recently, but in most cases wizard related issue are caused by caching, server configuration, or a plugin/theme conflict.
To help us investigate further, could you please share the following:
System Status Report (WooCommerce > Status > Get system report)
Any fatal error logs under WooCommerce > Status > Logs
The thread where you left your response is not related to the issue you’ve described here, and the other thread was created almost five months ago. Please share your system status report as requested earlier so I can better understand your setup and provide more tailored assistance.
For reference, here is a video of me going through the setup wizard on a fresh WordPress installation with a new WooCommerce setup: https://www.loom.com/share/205820e5d7f0414d82176171593e86eb as you’ve requested. Will be looking forward to your response.
Thanks again for the update and for sharing your system report.
I’ve just tested the setup wizard on a clean install running WordPress 6.9, WooCommerce 10.3.6, and PHP 8.2.5, and it loads and completes successfully. Here’s a quick recording of the process: https://streamable.com/ttd531.
I understand you’ve already tried disabling plugins and switching to the default Twenty Twenty-Five theme, and still encountered the Cannot read properties of undefined (reading 'title') error. Given that, and the fact that you’ve seen similar reports from other users recently, I agree this could be worth deeper investigation.
From your system report, your environment looks solid: memory limit, PHP version, database, and WooCommerce setup all check out. One thing that stands out is the size of your wp_postmeta table (665MB), which is unusually large for a fresh install. While not necessarily the root cause, it could contribute to unexpected behavior in some admin screens.
To help isolate the issue further, could you try the following steps again? Just to rule out any residual conflicts or caching effects:
Clear both your site cache and browser cache thoroughly (seemed to have worked for a similar issue in the past).
Temporarily deactivate all plugins except WooCommerce.
Switch to the default Twenty Twenty-Five theme again.
Then retry the setup wizard and let us know if the error still appears.
I know you’ve already done some of this, but repeating the steps after clearing cache and with the latest WP build might help us confirm whether it’s truly environmental or something deeper in WooCommerce.
Appreciate your patience and persistence. Looking forward to your update.
Thanks for the well written and professional response Frank.
I have tried disabling all the plugins, switching themes and trying the setup wizard again. It still crashes with the exact same response.
Would you be able to tell me what this script is looking for exactly so I can ensure my setup has the correct value it needs? Basically, I’m thinking we should do some advanced debugging to try and find the root cause of the issue.
Thank you for the clarification, for following the steps suggested by Frank, and for your follow-up.
I’ve looked further into the issue and tried to trace the file. I noticed that the core-profiler folder does exist in the WooCommerce repository, as shown in your screenshot, but I wasn’t able to locate any file named core-profiler.js.
As a first step in troubleshooting, please try running the setup wizard in incognito mode with no browser extensions active. This will help rule out any conflicts caused by browser extensions. You can also try a different browser. For example, if you were using Chrome, try Chrome incognito, and also test in Opera or Firefox incognito to see if the behavior remains the same.
Please share your observations after trying this so we can determine the next steps for further troubleshooting. I’ll be looking forward to your response.
I have tried that before. I tried both Chrome and Firefox in private browsers which have no previous cookies or cache present. The same issue persists.
Thank you for getting back and for the clarification@cybsys,
Can you try accessing your WordPress installation folder and use your control panel’s search function to look for a file named core-profiler.js? Please let me know if you find it and which folder it’s located in. This will help us determine whether the console error is related to the issue you’re experiencing or if it might be triggered by another plugin or loaded from a different location.
Okay, from looking at the codebase on GitHub, the JavaScript wants data from the REST API. Since it cannot get any data via REST, it throws that exception.
So the next question would be, why is REST failing…
Thank you for your update and for getting back to us. I was also able to trace the issue on my local installation eventually.
So far, we’ve attempted several ways to replicate the problem but haven’t succeeded. Two things still stand out: first, as Frank mentioned, your database file size is unusually large for a new installation. Second, I noticed you’re using a custom child theme of Blocksy, which includes custom templates for some WooCommerce pages, as shown below. I understand you’ve tested with the 2025 theme, but my suspicion still leans toward these two factors.
Could you share a copy of the child theme you currently have installed so I can test it on a fresh installation on my end? Additionally, please try creating a new WordPress installation on the same server. Can be a directory or subdomain. Then install the Storefront theme, and set up WooCommerce. Let me know if the issue you’re experiencing on your main site also occurs there.
