• Resolved Brian P

    (@bburgay)


    We have a site which already has a “Checkout” page using the “checkout” slug. This is used for product buybacks with a custom plugin and theme page template.

    I renamed the default WooCommerce Checkout page and slug to “Shop Checkout” and “shop-checkout” but when I go to our checkout page with slug “checkout” I still get the “Our store is in the works and will be launching soon!” message which is overriding our non-WooCommerce checkout page.

    I verified the WooCommerce Checkout page is set to “Shop Checkout” with the correct ID in WooCommerce > Settings > Advanced and tried saving it again in WooCommerce > Settings > Advanced to see if that would fix it, but it’s still putting our custom non-WooCommerce checkout page in coming soon mode.

    I verified this will break any page with slug “checkout” too (not a page using a page template).

    If the Checkout page in WooCommerce > Settings > Advanced is set to something other than the default, coming soon mode should not be affecting a non-WooCommerce page with slug “checkout”. Is there a hook or filter I can use to fix this, or can you please fix this in WooCommerce?

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thanks for reporting this! @bburgay

    Could you please confirm if you are still encountering this issue in version 9.8? The issue was addressed in WooCommerce 9.8. If the problem persists, we would appreciate your feedback!

    In the meantime, if you’re looking for a workaround, WooCommerce also includes a filter to exclude specific requests from Coming Soon mode: woocommerce_coming_soon_exclude. If needed, You can bypass Coming Soon mode for your custom /checkout page.

    add_filter( 'woocommerce_coming_soon_exclude', function( $excluded ) {
    // Get the current request URI, e.g. /checkout/
    $request_uri = trim( $_SERVER['REQUEST_URI'], '/' );

    // If the request is for the custom checkout page, exclude it from Coming Soon mode
    if ( $request_uri === 'checkout' ) {
    return true;
    }

    return $excluded;
    } );

    Let us know what version you’re using and if the issue persists after updating!

    Hi @bburgay,

    To make your store live, go to WooCommerce > Settings > Site Visibility and choose Live. This will publish your store and remove the “Coming Soon” message or notice.

    Thread Starter Brian P

    (@bburgay)

    Hi @chihsuan,

    Thanks for the reply! Yes, I’m using version 9.8. I just installed it on this site yesterday actually, so it’s 9.8.1 with no update available and the bug is still there. So doesn’t look like it was actually fixed in 9.8.

    I tried the filter you gave as a workaround for now and it works great. Exactly what I was looking for. Thanks! When I’m logged in as an admin I still get the “This page is in ‘Coming soon’ mode and is only visible to you and those who have permission.” message at the bottom of the screen though which is annoying.

    Hopefully they can get this fixed in the next update. We should not have to worry about WooCommerce hijacking and breaking non-WooCommerce pages!

    Thread Starter Brian P

    (@bburgay)

    Hi @mosesmedh,

    Yes, obviously I can just turn Coming Soon mode off but that doesn’t fix the problem. What if we want to use Coming Soon mode for store pages only? I should never have to worry about WooCommerce hijacking and overriding very important non-WooCommerce pages.

    Zee

    (@doublezed2)

    Hello Brian P,

    Thank you for your reply.

    I am glad to know that you were able to resolve the issue using the custom code provided by @chihsuan. I understand this is a temporary fix and WooCommerce should fix this by default.

    @chihsuan, I appreciate your contribution here. How did you determine that this issue was fixed in WooCommerce 9.8? I want to confirm whether this has been reported on GitHub.

    Have a great day!

    Hi @bburgay, @doublezed2,

    Thanks for confirming!

    I’ve re-checked the behavior in WooCommerce 9.8.1. I can confirm that the issue persists: Coming Soon mode is incorrectly affecting non-WooCommerce pages with the /checkout slug, even when the actual WooCommerce checkout page has been reassigned in settings.

    This shouldn’t happen, and I’ll work on a proper fix that applies only to the actual WooCommerce store pages.

    Jonayed (woo-hc)

    (@jonayedhosen)

    Hi @chihsuan ,

    Thanks for creating the PR! Hopefully, the communication will continue there. You’ll be notified if our developers need your attention for any further details.

    We really appreciate your contribution—thank you again for helping us improve things!

    Having this issue on 9.8.2

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @manfromnapa

    I understand that you have a somewhat similar problem.

    However, per forum best practices shown here, it is advised that you create a new thread so that we can address your issue(s) separately.

    You can create a new thread here: https://wordpress.org/support/plugin/woocommerce/#new-topic-0 and make sure to include as much information as you can.

    Thanks for understanding!

    Plugin Support Kay U a11n

    (@kingsleyinfo)

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

    If you have a few minutes, we’d love if you could leave us a review: https://wordpress.org/support/plugin/woocommerce/reviews/

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Coming Soon “Apply to store pages only” Breaks Other Checkout Page’ is closed to new replies.