Likes: fix disabled bug

[arcangelini]

Closes https://linear.app/a8c/issue/CML-1013/likes-notification-and-email-delivery-issue-for-renwulfcreationscom-no

Proposed changes:

• Enable likes option sitewide when the Likes button is rendered

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)?

Currently the Likes block enables the ability to like a post, but without the wpl_is_enabled_sitewide setting enabled we do not have notifications being handled. Forcing this to be true should solve the issue.

I chose to use the sitewide setting rather than the post since this block could and likely exists in a template or reusable block.

Jetpack product discussion

n/a

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

No

Testing instructions:

1. Disable Likes on your tests site wide sharing options.
2. Create a new post and make sure the Like option is also disabled in the post settings.
3. Publish the post and make sure there is no like button or ability to like the post.
4. Add a Like button to the post, save, and try again.
5. You should be able to like the post AND the owner should get a notificatio.

[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 fix/like-disabled-with-block branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/like-disabled-with-block

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 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/extensions/blocks/like/like.php	0/75 (0.00%)	0.00%	1 ❤️‍🩹

Full summary · PHP report · JS report

[jeherve]

make sure the Like option is also disabled in the post settings.

I struggled with that part of the test as I was testing on self-hosted, where that option is no longer available.

On WordPress.com simple, I am able to toggle this option on and off, but I think my testing environment was different from yours. I added a Like block to my theme's single posts template. When doing so, the Like button appears under all posts on the site, regardless of that "WordPress.com Likes are Turned on per post" option. However, I am not able to Like posts. I get a JavaScript error (Uncaught TypeError: can't access property "parentNode", wplbuttonlink is null) which I think is caused by a different issue (the Like block markup is a bit different from the legacy Like markup).

Did you test this differently?