Jetpack Search: Display new plans

[gibrown]

All of this should get hidden behind a feature flag initially i guess.

There are a number of places the new plans need to get displayed:

• https://wordpress.com/plans/gibrown.wpsandbox.me::main (both yearly and monthly). Copy from Jetpack Backups as a start. (Fixed by Jetpack Search: Display in plans page #39942)
• https://wordpress.com/plans/my-plan/gibrown.wpsandbox.me::main (In progress at Jetpack Search: Display in My Plans page #40382)
• wp.com sites need to also have plans working (but lower priority)
• checkout page needs to work ala https://wordpress.com/checkout/gibrown.wpsandbox.me::test0/jetpack_backup_realtime
• we need to be able to accept links from wp-admin into calypso to do a purchase also

I started some of the work on this in #39857

I suspect we should break this up into smaller issues. Maybe after creating a bunch of constants.

[jsnmoon]

https://wordpress.com/plans/my-plan/example.com currently doesn't display any information about Jetpack Single Products. Do we intend to add something here? @gibrown @keoshi

[keoshi]

@jsnmoon It actually does show single products on a separate block:

Seems to come from here:

wp-calypso/client/my-sites/plans/current-plan/purchases-listing.jsx

Line 214 in 9af6717

renderProducts() {

So it might be simple(r) to plug Search in, even though it would require some tweaks; e.g.:

wp-calypso/client/my-sites/plans/current-plan/purchases-listing.jsx

Line 83 in 9af6717

getJetpackBackupPurchase() {

[jsnmoon]

@keoshi didn't expect you to be awake 😆

Thanks for the lead! I'll mess around with the code in that area.

[jsnmoon]

wordpress.com/plans/my-plan/gibrown.wpsandbox.me::main

It looks like implementing the interface for /plans/my-plan/ will have to wait until we can query the Search product purchases:

wp-calypso/client/my-sites/plans/current-plan/purchases-listing.jsx

Line 252 in 9af6717

<QuerySitePurchases siteId={ selectedSiteId } />

@DavidRothstein, is my assumption here correct?

[AnnaMag]

To check for UX/copy completeness :

the steps in the flow leading from the jetpack.com/pricing page (tested being logged in):

• selecting a paid plan (non-Pro)
• filling in the remote install url input form
• JPC recognizes pre-selected plan and skims through the plans grid landing at /checkout with the annual purchase option. Side Q: there is no alternative path should users change their minds or want to explore monthly (but close the page)
  The JPS Solution is available in the /plans tab afterwards, but not presented anywhere in the above flow.

Intercepting this connection flow from /pricing may not be a goal as JPS has its dedicate landing page at jetpack.com/upgrade/search/ and own remote install redirect, but since it involves plans page in the process, flagging it here.

/cc @keoshi

[DavidRothstein]

@jsnmoon If you have a Jetpack Search subscription on your site, I think QuerySitePurchases would already return it. That endpoint just returns all the subscriptions for a site, so it should include Jetpack Search.

Trying to test it now, though, I wasn't actually able to add a Jetpack Search subscription to a site in the first place, either in Calypso or via the backend admin... in Calypso the shopping cart just seems to get emptied when you add it to the cart, and in the backend admin you get an error about it not being available for a Jetpack site. There may be something wrong with the way the product is set up. But once that is fixed and it is possible to add the subscription, I expect it to be returned from the purchases endpoint automatically.

[DavidRothstein]

Trying to test it now, though, I wasn't actually able to add a Jetpack Search subscription to a site in the first place, either in Calypso

Ah, I see that's actually one of the tasks already listed at the top of this issue :)

checkout page needs to work ala https://wordpress.com/checkout/gibrown.wpsandbox.me::test0/jetpack_backup_realtime

Not entirely sure why it doesn't work automatically when you replace jetpack_backup_realtime with jetpack_search, but like I said above it is probably just some small missing thing in the product setup.

[gibrown]

I think this is all out of date, so closing