Blocks: update remaining child blocks to API version v3

[jeherve]

Fixes #40678

Proposed changes:

It seems that we had forgotten to update a few of our child blocks in #34120.

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

• N/A

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

• No

Testing instructions:

Note

1. You'll need to test all the blocks touched by this PR on a site running Gutenberg (can be a simple site for example), and not using Gutenberg (can be a fresh JN site).
2. To test the recipe block on non-simple sites, you will need to add a filter to your site on self-hosted (add_filter( 'jetpack_blocks_variation', function () { return 'beta'; } );) or use the option in Settings > Jetpack constants on JN. On simple sites, you will get the Beta blocks if you are proxied.

1. Before you switch to this branch, create posts with each one of the touched blocks.
2. Then switch to this branch.
3. Edit each one of the posts and ensure that there are no errors in the console, that the blocks can still be edited, and that they look good on the frontend (still use the right CSS classes).

[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 fix/child-blocks-api-version-v3 branch.

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

  bin/jetpack-downloader test jetpack fix/child-blocks-api-version-v3
  

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!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for January 7, 2025 (scheduled code freeze on undefined).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[coder-karen]

Thank you for following up on this!

I tested each of the child blocks on Simple, WoA and self-hosted (Jurassic Ninja).

On WoA, Simple and self-hosted (both with and without Gutenberg installed and active for WoA and self-hosted), I noticed issues with the PR applied in both the Contact Info block and WhatsApp button, but only in the editor.

With the WhatsApp button, styles appear to be missing for the button:

With the Contact Info block, in both WoA and self-hosted I'm having issues adding content in the editor (the fields appear generally un-editable, and once a few are added, no new fields seem to reappear).

I saw no relevant console errors.

On Simple, I was additionally seeing block validation issues within the Recipe block both before and after the change (so, unrelated). I'll note it down anyway here:

One inner block with issues was for recipe details:

Content generated by `save` function:

<div class="wp-block-jetpack-recipe-details"><div class="wp-block-jetpack-recipe-details__detail"><p>Prep Time</p><p itemprop="prepTime" content="PT15M">15m</p></div><div class="wp-block-jetpack-recipe-details__detail"><p>Cook Time</p><p itemprop="cookTime" content="PT30M">30m</p></div><div class="wp-block-jetpack-recipe-details__detail"><p>Servings</p><p itemprop="recipeYield">4</p></div><div class="wp-block-jetpack-recipe-details__detail wp-block-jetpack-recipe-details__detail--print"></div></div>

Content retrieved from post body:

<div class="wp-block-jetpack-recipe-details"><div class="wp-block-jetpack-recipe-details__detail"><p>Prep Time</p><p itemprop="prepTime">15m</p></div><div class="wp-block-jetpack-recipe-details__detail"><p>Cook Time</p><p itemprop="cookTime">30m</p></div><div class="wp-block-jetpack-recipe-details__detail"><p>Servings</p><p itemprop="recipeYield">4</p></div><div class="wp-block-jetpack-recipe-details__detail wp-block-jetpack-recipe-details__detail--print"></div></div>

The other inner block with issues was for recipe steps:

Content generated by `save` function:

<ol itemscope itemprop="recipeInstructions" itemtype="https://schema.org/HowTo" class="wp-block-jetpack-recipe-steps"></ol>

Content retrieved from post body:

<ol itemprop="recipeInstructions" class="wp-block-jetpack-recipe-steps"></ol>

[coder-karen]

I looked into this some more. With the Send a Message / WhatsApp button block, it looks like wrapping the returned content in a div with blockProps may solve that particular issue: <div { ...blockProps }> For that, useBlockProps also needs to be imported from '@wordpress/block-editor'
and then const blockProps = useBlockProps();. Though in my testing the HTML was ever so slightly different, so may need some tweaking.