feat(content-gate): implement restriction rules

[miguelpeixe]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

Depends on #4265

Implements the restriction rules as designed in #4265.

How to test the changes in this Pull Request:

1. Deactivate Woo Memberships
2. Create multiple gates, one for each available access and content rule (post type, category, and tag)
3. Create a post that matches one of the gate content rules (tag or category)
4. Use wp shell to execute Newspack\Content_Restriction_Control::get_post_gates( $post_id );
5. Confirm you get the correct gates
6. Edit the post to match other (multiple) gate rules
7. Restart the shell and run Newspack\Content_Restriction_Control::get_post_gates( $post_id );
8. Confirm you get the correct gates
9. The rule evaluation logic wasn't changed, but the logic that implements it for restriction was. Edit a gate access rule to run behind a subscription
10. As a reader without the subscription, confirm the gate renders in content restricted by it
11. As a reader with the subscription, confirm you have access to the content

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you successfully ran tests with your changes locally?

[Copilot]

Pull request overview

This PR implements restriction rules for content gates, refactoring the logic from metadata-based matching to a rule-based system. The changes enable more flexible content restriction by supporting multiple content rule types (post types, categories, tags) that must all match for a gate to apply to a post.

Key Changes:

• Refactored get_post_gates() to evaluate content rules (post type, taxonomy terms) using a new rule structure instead of post metadata
• Modified is_post_restricted() to use the refactored gate matching and track which gate restricts each post via $post_gate_id_map
• Enhanced restrict_post() with additional checks to ensure only singular posts matching the queried object are restricted

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
includes/content-gate/class-content-restriction-control.php	Implements content rule evaluation logic, adds gate ID tracking via static property, and introduces get_gate_post_id() filter callback to retrieve the restricting gate for each post
includes/content-gate/class-content-gate.php	Adds singular/queried object checks to restrict_post(), simplifies is_post_restricted() return logic, adds post ID parameter to gate filter, ensures minimum visible paragraphs, and removes unused description field from gate structure

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dkoo]

@miguelpeixe I ran into a handful of issues testing this PR. Because I wasn't sure if they were because of the changes here or just due to all of the merges and PRs we've done around these features lately, I opened two new PRs to fix them on my local site:

• #4338
  • Fixes several issues with the sanitize_gate method (UI has no expected description field, sanitize_access_rule converts an array of product IDs to strings via sanitize_text_field, etc)
  • Changes the UI element for selecting subscription products to a FormTokenField: the UI only let you choose a single value, but the back-end expects an array of values.
  • Corrects the content rule slug when evaluating the post_types rule (note plural)
  • Fixes a fatal error due to mismatched parameters from the newspack_content_gate_restrict_post filter hook in class-content-gifting.php
• Automattic/newspack-blocks#2264
  • I'm not sure why this is happening only with this branch, but I was seeing a fatal after a successful modal checkout while on this branch. This PR should fix the fatal and ensure that the custom thankyou.php template is shown after a modal checkout transaction.

If the changes in these PRs look good, feel free to merge them and I can re-test!

[miguelpeixe]

Thank you for addressing them! I've also faced issues while retesting, and it looks good in your branch.

[dkoo]

Working with the fixes applied!

[github-actions]

Hey @miguelpeixe, good job getting this PR merged! 🎉

Now, the needs-changelog label has been added to it.

Please check if this PR needs to be included in the "Upcoming Changes" and "Release Notes" doc. If it doesn't, simply remove the label.

If it does, please add an entry to our shared document, with screenshots and testing instructions if applicable, then remove the label.

Thank you! ❤️

[matticbot]

🎉 This PR is included in version 6.28.0-alpha.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 6.28.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀