Jetpack: Plans: support developers to test plans on multiple staging sites

[gibrown]

It is currently tricky for a developer to test paid features for clients. They would need a plan for each and every staging site that they are developing for.

We should consider a couple of options:

• Discounts for multiple plans so at least a dev can have multiple plans easily
• Ability to change plans with more granularity than one month
• Moving the activated plan between different sites
• A "staging site" license that goes with any production pro site and can be used on sites that are non-production

[stale[bot]]

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

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

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[chickenn00dle]

A case of this here: 1580580-zen / 8184594-hc

I had a user in chat who wanted to test a premium theme on staging before updating their live site.

They obviously couldn't without adding an appropriate Jetpack plan for staging.

Seems like this type of thing would be pretty common.

[stale[bot]]

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

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

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[hubertnguyen]

You could also have some kind of free Tiers where all the features are available for a relatively small number of requests. That would be enough for developers or stagging areas, but not quite to enter production even for a modest site.

Alternatively, Jetpack could switch to that limited mode if the site is not publicly accessible. We often edit our host file to access development sites. In any case, it would be very handy to get full Jetpack features in non-production systems.

For example, we pay for and have access to the Jetpack Related Search, but since we don't want to use the widget, we need access to the API on the development system.

At the moment, I think that the only way to test is to create a private page and resort to "cowboy coding" on the live site on a custom post type or something to reduce the possibilities of errors. Can be done, but not great.

[RCowles]

Noting that this was also requested in 2799792-zen.

[maxledoux]

+1 for this feature, please.

You could link the staging site to the live site using a constant defined by the user in wp-config.php. If the staging site has a defined live site, and the live site has a premium plan, then all the paid features of the live site would work on the staging site. You could add a banner, I guess, on the staging site, that read something like "staging site for " so that people wouldn't try to cheat and use one premium plan on multiple live sites. I wouldn't mind that, as long as it wasn't too big and annoying.

[stale[bot]]

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

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

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.