Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checkout: Update support section in generic Thank You page #3943

Closed
stephanethomas opened this issue Mar 10, 2016 · 3 comments
Closed

Checkout: Update support section in generic Thank You page #3943

stephanethomas opened this issue Mar 10, 2016 · 3 comments

Comments

@stephanethomas
Copy link
Contributor

In some very rare cases we have to display a generic Thank You page. This happens when the API failed to return a receipt and the corresponding list of purchases. However we shouldn't probably display a placeholder for the support section when that happens:

screenshot

@breezyskies, @mikeshelton1503, what do you think? It looks like we have three options :

  1. Hide the support section entirely
  2. Display (force) the WordPress.com version of the support section instead of the placeholder
  3. Wait until @peterbutler has fixed the API and retire this generic page :)

Note this issue should probably be addressed at the same time than #3932.

@stephanethomas stephanethomas added the [Feature] Checkout The checkout screen and process for purchases made on WordPress.com. label Mar 10, 2016
@fabianapsimoes fabianapsimoes added Post Checkout [Type] Enhancement and removed [Feature] Checkout The checkout screen and process for purchases made on WordPress.com. labels Mar 10, 2016
@stephanethomas stephanethomas added this to the Amber: Backlog milestone Mar 10, 2016
@breezyskies
Copy link
Contributor

Wait until @peterbutler has fixed the API and retire this generic page :)

I think we should keep the generic page as a fallback regardless of the API fixes. It's a good fallback for other scenarios that may be outside our control (or knowledge) -- like a new product being added.

Between options #1 and #2, I think forcing the WordPress.com support section is probably the way to go. It's possible that we're sending them to the wrong support, but then they can get directed to the right place (and this should be for minimal cases). They just paid us money (and in some cases, something possibly went wrong), so I wouldn't want to leave them with no hint of support options.

@fabianapsimoes
Copy link
Contributor

Display (force) the WordPress.com version of the support section instead of the placeholder

We had a similar discussion when working on the support section for other Thank You pages (#3755 (comment)). In the end, we decided to use placeholders since the support URL can change depending on either we're dealing with a Jetpack prodcut or not. We should probably remain consistent in terms of that behavior.

@stale
Copy link

stale bot commented Jan 11, 2018

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week. If you would like it to remain open, can you please comment below and see what you can do to get things moving with this issue? Thanks! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants