Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

When you try to change the Checkout endpoint to "check" it appends "-2" automatically #10553

Closed
namiokuzono opened this issue Aug 11, 2023 · 2 comments
Labels
type: bug The issue/PR concerns a confirmed bug.

Comments

@namiokuzono
Copy link

namiokuzono commented Aug 11, 2023

Describe the bug

When you try to change the Checkout endpoint to "check" it appends "-2" automatically

To reproduce

Steps to reproduce the behavior:

  1. Newly install WP installation and set up Woo
  2. Try changing the endpoint for checkout to "check" (WooCommerce > Settings > Advanced > Page Setup > Checkout > Try changing the endpoint from "checkout" to "check")
  3. This would append "-1" automatically, so it looks like "check-2"

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Screen Recording: https://woonami.xyz/c114RFpz

Environment

WordPress (please complete the following information):

  • WordPress version: 6.3
  • WooCommerce version: 8.0.1
  • WooCommerce Blocks version: 10.8.3
  • Site language: en_US
  • Any other plugins installed:
    • Code Snippets: by Code Snippets Pro – 3.4.2
    • Companion Plugin: by Osk – 1.30
    • Jetpack: by Automattic – 12.4
    • WooCommerce: by Automattic – 8.0.1
    • WordPress Importer: by wordpressdotorg – 0.8.1
    • (Inactive) Akismet Anti-Spam: Spam Protection: by Automattic - Anti Spam Team – 5.2
    • (Inactive) Hello Dolly: by Matt Mullenweg – 1.7.2

Desktop (please complete the following information):

  • OS: macOS
  • Browser: Chrominium/Vivaldi
@namiokuzono namiokuzono added the type: bug The issue/PR concerns a confirmed bug. label Aug 11, 2023
@senadir
Copy link
Member

senadir commented Aug 15, 2023

I'm unable to reproduce this locally.

WordPress would append -2 if an existing page with that slug already exists, so check for that?

@mikejolley
Copy link
Member

Thanks for the report @namiokuzono. I've just seen this issue and can confirm it was noticed and fixed in #10640, so the latest release of blocks should have cleared this up.

Thank you

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug The issue/PR concerns a confirmed bug.
Projects
None yet
Development

No branches or pull requests

3 participants