Jetpack Search: enable purchases via "...search/yearly" routes. #43865
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this Pull Request
/jetpack/connect/jetpack_search/yearly
and/jetpack/connect/wpcom_search/yearly
routes.At the moment inputting urls is disabled at those screens. We use
/jetpack/connect/jetpack_search
for yearly product type, but since /yearly had been defined as a route, we should keep it functional.Also, here we adapt product type definition such that it is independent of the actual route.
Second fix is processing purchases for Jetpack sites- we correct the condition that moderated WP.com vs. JP site type of product at checkout. It was adding an empty product and as such, redirecting to /plans.
Testing instructions
/jetpack/connect/(jetpack|wpcom)_search/yearly
and verify the purchase process.