Remove customization for hiding Core's start page options modal

[okmttdhr]

Related to

• ETK: Hide the start page options modal from Core wp-calypso#83750
• Bug: core/post-content is stripped out of registered patterns blockTypes property for WPCOM sites wp-calypso#98892

Proposed changes:

Remove update_pattern_block_types since;

• we should fix the bug where core/post-content is stripped out of registered patterns. Bug: core/post-content is stripped out of registered patterns blockTypes property for WPCOM sites wp-calypso#98892
• Core's start page options modal was replaced with the sidebar.
  • I believe we can remove our whole starter page template modal, but this PR focuses on removing update_pattern_block_types only.

See p1737695864171759/1737538662.329279-slack-C03N25JPCE4 for more context.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Patch this PR by following the instructions in Remove customization for hiding Core's start page options modal #41324 (comment)
• Create a new page
• Ensure our starter page template modal is displayed correctly
  • 
  • i.e., Ensure Core's start page options modal isn't displayed
    • on Core:

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the update/remove-update_pattern_block_types branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/remove-update_pattern_block_types
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• 🔴 Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[fushar]

👍 I can confirm that the dotcom page starter modal still works fine after this change. However, I didn't check whether it fully resolves Automattic/wp-calypso#98892 (needs @triple0t 's help to verify)

[triple0t]

I tested on my WoA site and can confirm this PR resolves the issue.
Thank you.