Skip to content

Forms: Remove duplicate display of form blocks under the Jetpack block inserter section#47614

Open
DevinWalker wants to merge 1 commit intotrunkfrom
fix/dont-list-form-blocks-twice
Open

Forms: Remove duplicate display of form blocks under the Jetpack block inserter section#47614
DevinWalker wants to merge 1 commit intotrunkfrom
fix/dont-list-form-blocks-twice

Conversation

@DevinWalker
Copy link
Contributor

Fixes #

Proposed changes

  • Removes the registerBlockCollection('jetpack', ...) call from block-category.js that caused all jetpack/* namespace blocks to appear in both their own proper category (Forms, Monetize, Grow, Text, Media, etc.) and a redundant "Jetpack" collection panel in the block inserter.
  • Removes the now-unused registerBlockCollection PHP flag from Jetpack_Editor_Initial_State in class.jetpack-gutenberg.php.

Every Jetpack block already has a specific category assigned, so the "Jetpack" collection provided no additional discoverability — it only created confusing duplication, particularly for Forms blocks which appeared under both "Forms" and "Jetpack".

Other information

  • Generate changelog entries for this PR (using AI).

Related product discussion/links

JETPACK-1418 (peKye1-1418-p2)

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

No.

Testing instructions

  1. Activate Jetpack on a WordPress site.
  2. Open the block editor on any post or page.
  3. Open the block inserter ("+" button) and click "Browse all".
  4. Verify that form-related blocks (Form, Text input field, Number field, Radio, etc.) appear only under the Forms category — not under a separate "Jetpack" section.
  5. Verify other Jetpack blocks (e.g., Map, Subscription Form, Donations) still appear under their own correct categories (Embed, Grow, Monetize, etc.).

Made with Cursor

…k inserter section

Removes the `registerBlockCollection('jetpack', ...)` call that caused all
`jetpack/*` namespace blocks to appear in both their own category (Forms,
Monetize, Grow, etc.) and a redundant "Jetpack" collection panel. Every
Jetpack block already has a specific category, so the collection provided
no additional discoverability.

Made-with: Cursor
@DevinWalker DevinWalker added the [Status] Needs Review This PR is ready for review. label Mar 16, 2026
@DevinWalker DevinWalker self-assigned this Mar 16, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 16, 2026

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 WoA dev 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 (Jetpack), and enable the fix/dont-list-form-blocks-twice branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack fix/dont-list-form-blocks-twice

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 github-actions bot added the [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ label Mar 16, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 16, 2026

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 Review, ...).
  • ✅ 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 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, 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 as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
  • WoA releases happen weekly.
  • Releases to self-hosted sites happen monthly:
    • Scheduled release: March 31, 2026
    • Code freeze: March 31, 2026

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

@jp-launch-control
Copy link

Code Coverage Summary

Coverage changed in 2 files.

File Coverage Δ% Δ Uncovered
projects/plugins/jetpack/class.jetpack-gutenberg.php 168/448 (37.50%) 0.08% -1 💚
projects/plugins/jetpack/extensions/shared/block-category.js 0/6 (0.00%) 0.00% -2 💚

Full summary · PHP report · JS report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] Needs Review This PR is ready for review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant