Jetpack: Auto-activate Subscriptions

[oskosk]

Makes subscriptions enabled by default

I'm still deciding on whether these options should be set to false as they affect the frontend. Already tackled in a91df30

Fixes #14621

Proposed changes:

• Updates the header of modules/subscriptions.php to have Auto-activate: yes

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?

No

Testing instructions:

• Launch a JN site with this branch
  
• Create a post
• Connect Jetpack
• Attempt to add a Subscrible block. Confirm you can.
• Visit the frontend sample post and confirm the checkboxes for subscribing are not there

Like this	Not like this

• Visit Jetpack Settings and confirm they're by default like this:

[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.
  
• ✅ All commits were linted before commit.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team 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 🤖

---

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.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team review" label and ask someone from your team review the code.
Once you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

---

Jetpack plugin:

• Next scheduled release: March 7, 2023.
• Scheduled code freeze: February 28, 2023.

[github-actions]

Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run

bin/jetpack-downloader test jetpack update/jumpstart-subscriptions

to get started. More details: p9dueE-5Nn-p2

[jeherve]

Related:

• Subscriptions block: Make it always available #14621
• Gutenberg: Enable Contact Form block by default / Block Discoverability #10903

I'm still deciding on whether this options should be set to false as they affect the frontend

I would personally vote for keeping this opt-in, to stay consistent with the other Jetpack features that impact the frontend of a site.

[oskosk]

I would personally vote for keeping this opt-in, to stay consistent with the other Jetpack features that impact the frontend of a site.

Cool. I just pushed a91df30 to see if I'm doing it properly. Need to wait for a fresh JN to be able to test this change.

[oskosk]

@jeherve I think #10903 is not related. The contact form block is already available after connection. Would you mind clarifying in case I'm missing something?

[jeherve]

You're right, I meant to add #28288. This was an autocomplete fail on my end, sorry, I tabbed too quick.

Noting that we've also been discussing this in Automattic/wp-calypso#71714

[github-actions]

This PR has been marked as stale. This happened because:

• It has been inactive in the past 3 months.
• It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, etc.

No further action is needed. But it's worth checking if this PR has clear testing instructions, is it up to date with trunk, and it is still valid. Feel free to close this PR if you think it's not valid anymore — if you do, please add a brief explanation.

[github-actions]

This PR has been automatically closed as it has not been updated in some time. If you want to resume work on the PR, feel free to restore the branch and reopen the PR.