DO NOT MERGE Forms: enable Hostinger Reach integration

[edanzer]

DO NOT MERGE: We're waiting for partner approval before merging.

Fixes FORMS-413

Proposed changes:

Enables Hostinger Reach integration by flipping feature flag default from false to true. While the integration was already tested when merged, it would worth re-testing before we release.

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

See Linear project.

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

No.

Testing instructions:

• Integrations dashboard. Confirm Hostinger shows in the dashboard integrations list, and that you can install, activate, and connect the service.

  • Install/Activate plugin. If not done already, install plugin from from the integrations dashboard, confirm plugin installs and activates, and confirm that card status updates once done.
  • Connect site. If you haven't connected Hostinger Reach already, you'll see button to complete setup. Click that to go to Hostinger settings page in your WordPress admin. Click the 'Connect Site' button and set up a free account.
  • Confirm connected state. After connecting site, go back to integrations dashboard. If needed click Refresh Status. Confirm that you no longer see buttons to install, activate, or complete setup, but rather just a link to the Hostinger dashboard. Confirm that links works.

• Integrations modal. Confirm Hostinger Reach shows in the block modal, and that you can enable it for the form and add a group name.

  • Create form. Create post with a new form. Be sure to include First Name, Last Name, and Email fields.
  • Integrations modal. Open the integrations modal. Confirm you see Hostinger Reach. Enable the integration with the header toggle. Add a Group Name.
  • Active integrations. Close the modal and confirm that the Hostinger icon now shows on the block sidebar.

• Form submission. Go to the frontend and submit your form.

  • No submit errors. Confirm no submit errors.
  • Contact added to Hostinger. Confirm contact is added to your Hostinger Reach account, and with the group name you added (or the default "Jetpack Forms" if you did not add a group name).

[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 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 update/forms-hostinger-feature-flag branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/forms-hostinger-feature-flag

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 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 🤖

---

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: December 2, 2025

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

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/contact-form/class-contact-form-plugin.php	457/1340 (34.10%)	0.45%	-6 💚
projects/packages/forms/src/contact-form/class-contact-form-endpoint.php	784/895 (87.60%)	1.90%	-17 💚

Full summary · PHP report · JS report