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.

Sign up for GitHub

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

Jump to bottom

Duplicate "Enable the new checkout" notices #3364

Closed
james-allan opened this issue Aug 19, 2024 · 1 comment
Closed

Duplicate "Enable the new checkout" notices #3364

james-allan opened this issue Aug 19, 2024 · 1 comment
Assignees
@james-allan
Labels
good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.

Comments

@james-allan
Copy link
Contributor

Describe the bug
If you have the legacy checkout experience enabled, you will see two banner notices on the Stripe payment method page.

Screenshot 2024-08-19 at 10 40 47 AM
Double Legacy checkout experience notices

To Reproduce
Steps to reproduce the behavior:

  1. Go to WooCommerce Stripe Settings.
  2. Enable the legacy checkout experience
  3. Go to the Stripe payment methods settings/list
  4. At the top of the settings you will see 2 notices.

Expected behavior
There should be only 1 notice.
@Mayisha Mayisha added the good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. label Aug 21, 2024
@diegocurbelo diegocurbelo added priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug. labels Aug 26, 2024
@james-allan james-allan self-assigned this Sep 23, 2024
@james-allan
Copy link
Contributor Author

Closing in favour of #3561 which has a PR (#3562)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@james-allan james-allan

Labels
good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@diegocurbelo @james-allan @Mayisha