filter to turn off Coming Soon Mode functionality

Hi @shawfactor

You can add this code snippet to your child theme’s functions.php to exclude all customer-facing pages.

add_filter( 'woocommerce_coming_soon_exclude', function() {
    return true;
}, 10 );

More info: https://github.com/woocommerce/woocommerce/blob/63d93d73551a1cc908e5385818796c9d042eca2f/docs/extension-development/integrating-coming-soon-mode.md#disabling-coming-soon-in-all-pages

I hope this helps! If you have any other questions, feel free to ask.

The snippet does not achieve what I want. I don’t want administrators to have this functionality at all.IE I don’t want them to use it or see it.

From readig the documentation the snippet stops the functionality from working in the front end but that still creates confusion on the back end.

Right now an admin sees an live button in the back end and can set coming soon etc in the back end. I don’t want them have this functionality or see it. We already have better functionality for this in our multisite platform.

More broadly why is this functionality part of the core woocommerce plugin? The functionality seems like it would make far more sense in its own extension…

• This reply was modified 6 months, 1 week ago by shawfactor.

Hi @shawfactor

Right now an admin sees an live button in the back end and can set coming soon etc in the back end.

Currently, there isn’t a direct filter to completely remove the site visibility mode from the backend. However, I found a pull request is in draft, which will provide an option to hide the level: https://github.com/woocommerce/woocommerce/pull/51398

In the meantime, you can use this code snippet to hide/remove this badge:

add_action(
    'admin_bar_menu',
    function ( $wp_admin_bar ) {
        $wp_admin_bar->remove_node( 'woocommerce-site-visibility-badge' );
    },
    100
);

Thanks again for your feedback. We appreciate your patience and understanding.

Thankyou for the snippet, it will definitely be useful.

you missed the bigger point I made in your PR though. But I’ve addressed that on github

Hi @shawfactor,

it will definitely be useful.

Glad to hear it.

you missed the bigger point I made in your PR though. But I’ve addressed that on GitHub

Our sincere apologies if we missed your larger point in the PR.

However, GitHub is the right place to having addressed this, as your contribution is invaluable to us, and we want to make sure all your concerns are taken into consideration. Our devs will take a look at the PR and make any changes where necessary.