CYS - Core: fix: not mark Customize your store step as completed when the user switches theme

[gigitux]

Submission Review Guidelines:

• I have followed the WooCommerce Contributing Guidelines and the WordPress Coding Standards.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have reviewed my code for security best practices.
• Following the above guidelines will result in quick merges and clear and detailed feedback when appropriate.

Changes proposed in this Pull Request:

Currently, the Customize your store step is marked when the user switches the theme. We disabled this beavhiour on Core.

How to test the changes in this Pull Request:

Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:

1. Head over to WooCommerce > Home.
2. Ensure that the Customize your store step isn't marked.
3. Switch theme.
4. Head over to WooCommerce > Home.
5. Click on Customize your store.
6. Click on "Start designing" and proceed to the Pattern Assembler.
7. Clic on "Done".
8. Head over to WooCommerce > Home.
9. Ensure that the Customize your store step is marked.

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

CYS - Core: fix: not mark Customize your store step as completed when the user switches theme

Comment

[github-actions]

Hi @albarin, @nefeline,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Hi @albarin,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Test Results Summary

Commit SHA: e0acffe

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 38s
E2E Tests	0	0	0	357	0	357	0m 0s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[nefeline]

@gigitux, I hope you don't mind: I've pushed a change here to ensure this fix also applies to WooExpress. As a second thought from our previous discussion, I think it's worth having all users benefit from this fix, not just core.