WooCommerce Setup Wizard keeps coming back

Hi @jpsvensson ,

I’m sorry to hear you’re still having trouble with the WooCommerce setup wizard in Chrome. Since this issue seems browser-specific, there is a workaround you can try. You can stop WooCommerce from promoting the setup wizard by adding the following code to your site’s functions.php file. For a safer approach, you can use the Code Snippets plugin:

add_filter( 'woocommerce_enable_setup_wizard', '__return_false' );

Please check and let us know if that helps!

Hi,
Thanks for the suggested fix but unfortunately it did not work. ??

I tried both with adding the code to /wp-includes/functions.php and with the Code Snippet plugin but nothing worked:

https://www.awesomescreenshot.com/video/37548507?key=5191ee80117f1368f8eb3079726d0339

Do you have any other suggestions? ??

Thanks!
Jonas

Hi @jpsvensson ,

Thanks for the update!

To troubleshoot further, Could you share a screenshot of your permalink settings? You can find this under WordPress > Settings > Permalinks Structure.

Also, if your .htaccess file has been modified, try backing up your .htaccess file and replacing it with the default WordPress rewrite rules to see if that helps:

# BEGIN WordPress
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

After updating .htaccess, be sure to: Flush permalinks by going to Settings > Permalinks in WordPress and clicking “Save Changes” (without making any changes).

Additionally, it would help if you could check what’s happening in your browser’s Network tab when the system redirects you to the WooCommerce Setup Wizard. Here’s how:

1. Open your browser console.
2. Switch to the Network tab.
3. Click on the WooCommerce tab.
4. Try triggering the redirect and take a full screenshot or a video of the files being logged during the process.

Let me know what you find!

Hi,
Thanks for not giving up!

Here are the Permalink Structure:
https://www.awesomescreenshot.com/image/53376809?key=6be3326617be761122df1b0a6bbbb1c4

I updated the .htaccess to your version and flushed the permalinks but that did not solve the problem.

Here is a video of the Network tab when the system redirects:
https://www.awesomescreenshot.com/video/37561941?key=054d5e795105f149410ecada7a93f13e

As you can see in the video there are 5 red errors. These are the URLs of the requests:

https://staging-1740768065.skogsbrynetstradgard.se/wp-json/wc-admin/onboarding/profile?_locale=user
https://staging-1740768065.skogsbrynetstradgard.se/wp-json/wc-analytics/admin/notes?page=1&per_page=5&status=unactioned&type%5B0%5D=info&type%5B1%5D=marketing&type%5B2%5D=survey&type%5B3%5D=warning&orderby=date&order=desc&_fields%5B0%5D=id&_fields%5B1%5D=name&_fields%5B2%5D=title&_fields%5B3%5D=content&_fields%5B4%5D=type&_fields%5B5%5D=status&_fields%5B6%5D=actions&_fields%5B7%5D=date_created&_fields%5B8%5D=date_created_gmt&_fields%5B9%5D=layout&_fields%5B10%5D=image&_fields%5B11%5D=is_deleted&_fields%5B12%5D=is_read&_fields%5B13%5D=locale&_locale=user
https://staging-1740768065.skogsbrynetstradgard.se/wp-json/wc-analytics/admin/notes?page=1&per_page=100&status=unactioned&type%5B0%5D=info&type%5B1%5D=marketing&type%5B2%5D=survey&type%5B3%5D=warning&orderby=date&order=desc&_fields%5B0%5D=id&_fields%5B1%5D=name&_fields%5B2%5D=title&_fields%5B3%5D=content&_fields%5B4%5D=type&_fields%5B5%5D=status&_fields%5B6%5D=actions&_fields%5B7%5D=date_created&_fields%5B8%5D=date_created_gmt&_fields%5B9%5D=layout&_fields%5B10%5D=image&_fields%5B11%5D=is_deleted&_fields%5B12%5D=is_read&_fields%5B13%5D=locale&is_read=false&_locale=user
https://staging-1740768065.skogsbrynetstradgard.se/wp-json/wc-analytics/reports/performance-indicators?after=2025-03-11T00%3A00%3A00&before=2025-03-11T23%3A59%3A59&stats=revenue%2Ftotal_sales%2Corders%2Forders_count&_locale=user
https://staging-1740768065.skogsbrynetstradgard.se/wp-json/wc-admin/onboarding/profile/progress?_locale=user

They all have this response:

<html><head><title>508 Resource Limit Is Reached</title><meta name='viewport' content='width=device-width'><link href='//splash.simply.com/errorpage.css' rel='stylesheet'></head><body><h1>508 Resource Limit Is Reached</h1><p>The website is temporarily unable to service your request as it is exceeding its resource limits. Please try again later.</p><h3>If you are the owner of the website:</h3><p>Most likely the maxmimum number of concurrent PHP-threads for your website have been reached. This can happen if the website is under heavy load and it is not optimized for it.</p><ul><li>Review the request logs.</li><li>Check your website resource usage (DISK-SPACE / CPU / RAM / IO).</li><li>Restart or investigate all running PHP-threads on your website.</li><li>Optimize your code execution.</li><li>Upgrade to a package with more resources.</li></ul><p>You can find a full overview of your resource usage in our Controlpanel.</p><hr><p>Z9H0D4Cpsuk8oCZ17nU8XgAAAEw - staging-1740768065.skogsbrynetstradgard.se - 194.237.172.129 - 20250312215231</p></body></html>

Is that of any help to you? Let me know if you need more details.

Thanks,
Jonas

• This reply was modified 1 week, 2 days ago by jpsvensson.

Hi @jpsvensson,

Thanks for sharing the screen recording and pointing out the errors you saw in the console. I understand how frustrating it must be to keep seeing the setup wizard despite completing it. No worries, I’ll walk you through the next steps to get this resolved.

Since you’ve mentioned that WooCommerce setup was completed successfully on Firefox and it does not prompt you again there, this confirms that the issue is specific to your Chrome browser, rather than your site or WooCommerce itself. This also explains why adding the filter using the Code Snippets plugin made no difference.

Also, from one of your earlier images (https://snipboard.io/Y96IyU.jpg), I see that one of the errors is “Store “core/interface” is already registered.”, which supports the fact that the store’s onboarding is completed. You can click the drop-down arrow to see more details about this error while on the console.

I recommend the following steps to resolve the issue in Chrome:

1. Clear your Chrome browser cache and cookies, then restart the browser and try again. Here’s how: https://support.google.com/accounts/answer/32050

2. Try using an incognito window (Chrome’s private browsing mode) and check if the issue persists.

3. If the issue still happens, uninstall and reinstall Chrome to ensure there are no lingering browser-related issues.

If clearing the cache and reinstalling Chrome doesn’t work, you may also need to clear the DNS cache of your site or any caching plugin you might have enabled.

Give these steps a try and let me know how it goes.

Hi,
Thanks for hangning in there!

1. I deleted all “Cached images and files – All time” and “Cookies and other sites data – All time” and restarted Chrome but that did not solve the problem.
2. I tried Chrome in Icognito mode but that did not solve the problem.
3. I uninstalled and reinstalled Chrome but that did not solve the problem.
4. I flushed the DNS cache with “ipconfig /flushdns” but that did not solve the problem.

I also tried my WordPress/WooCommerce on another computer and the problem was also shown there so I guess it is not computer related.

Let med know if you have any other suggestions. I will try anything at this moment! ??

Cheers,
Jonas

Hello jpsvensson,

Thank you for your reply.

I understand that the WooCommerce setup wizard keeps appearing in Google Chrome. You have tried clearing the browser cache, using incognito mode, reinstalling Google Chrome, and using Google Chrome on other computers.

This is a strange case because we have not received any other reports like this.
To investigate further, let’s try using another Chromium-based browser like Opera browser.
My goal is to determine whether there is something on the site that is incompatible with Chromium-based browsers.

I appreciate your patience while we try to figure out what is happening here. ??

Please let me know how it goes.

Best regards.

Hi,
Thanks for your patience!

I installed Opera and it shares the same problem:
https://www.awesomescreenshot.com/video/37649978?key=3552e2bcb34bc12d3c5f998ff785dd74

Here is the same site in Firefox the minute after without any sign of the problem:
https://www.awesomescreenshot.com/video/37650011?key=a094d13ba691ad30c26ac13974682d17

Here you can see that WooCommerce is the only plugin and that the default theme is active:
https://www.awesomescreenshot.com/video/37650201?key=09bff0c32bad57d6dc4a58c3cde7fb71

Please let me know if you need further details!

Thanks,
Jonas

Hi @jpsvensson,

Thanks for getting back to me and sharing those videos. They were helpful in understanding what you’re experiencing on your end. It seems like the issue is related to Chromium-based browsers, but we still need to determine whether it’s a request issue from your server or if something on your device is interfering with the browser when your site is opened.

I know there’s been a lot of back and forth, and I truly appreciate your patience as we do a bit more troubleshooting before concluding whether this is a bug.

Please install Local WP on your device: https://localwp.com/, then set up a new WordPress site on Local WP. Once that’s done, export a copy of your live site using All In One WP Migration or any other migration plugin and import it into the Local WP site. After that, try opening the Local WP site in Chrome or Firefox and let me know if the issue persists.

The goal of this test is to determine whether the issue originates from your server. If you’re unable to replicate the problem on Local WP, it might be a request issue from your live server. However, if the issue still occurs, continue with the troubleshoot steps below.

Next, try accessing your live site using Chrome or Opera on a different device than the one you’re currently using. Make sure this device is connected to a different internet network. After testing, please let me know what you observe.

Hi,
I installed a local WordPress and imported the site and everything works fine on local.

During the import this message was shown:
Your backup is from a PHP 7 but the site that you are importing to is PHP 8.

Could that be a clue?

I have also noticed that WooCommerce/Customers shows an error:
There was an error getting your stats. Please try again

This error could not be reproduced on the local site.

Do you have any suggestions on how to continue the troubleshooting?

Thanks,
Jonas

Hi there!

It seems the issue might be related to the PHP version not updating correctly on the hosting provider’s side. Since the import process showed that the backup was from PHP 7 but the site is on PHP 8, it’s possible that there is a server-side issue preventing the PHP version from updating as expected.

I would suggest reaching out to your hosting provider’s support team to verify the PHP version and make sure the environment is correctly configured for PHP 8. If they’re unable to resolve the issue or there are ongoing limitations with their service, you might want to consider testing with a different hosting provider to see if the issue persists.

Let me know how it goes, and I’m happy to assist further if needed!

Hi,

Thanks for hanging in there!

The WordPress is now running PHP version 8.3.8 but that did unfortunatley not fix the problem:

https://www.awesomescreenshot.com/video/37752839?key=b8936b69c494dcbc76d6867826478208

Do you have any other suggestions on the server side that might fix the problem?

Regards,
Jonas

Hello jpsvensson,

Thank you for your reply.

I understand that upgrading PHP to 8.3.8 on your live server did not resolve the issue.

I appreciate your efforts in troubleshooting; your findings have been very helpful. Since you have narrowed the problem down to your web server, it seems likely that something on the server is conflicting with Chromium-based browsers.

I recommend reaching out to your web host with all the details you’ve gathered, including the fact that the issue does not occur on your local server. They may be able to identify the root cause.

Let me know once you hear back from them.

Best regards.