Coming Soon Feature Conflicts with WordPress Privacy Setting and Private Sites
-
Hello,
I run a WordPress site with WooCommerce which can only be accessible to logged-in customers. The information and contents cannot be allowed to be scraped by search engines or accessed by non-authorised users. As such, the site is set to Private mode in the WordPress settings:
I can’t stress enough, we cannot set the site to Public / Live. My users use a secure link to automatically login to the site (for obvious reasons I can’t share here).When the update to add Site Visibility to WooCommerce was added to our account, we found that the Coming Soon setting which had been added, was redirecting users after their successful login to the Page Template ‘Coming Soon’ and seeing the message there and were stuck there. Prior to this, users would successfully hit the homepage where they should be re-directed to.
Naturally, the logical thing to do would be to activate the ‘Live’ setting on the Site Visibility on the WooCommerce and keep the WordPress privacy setting to ‘Private’.
However, this causes a major problem. Because when ‘Live’ is set in the WooCommerce Site Visibility setting, this overrides the WordPress privacy setting to ‘Public’. For us, this cannot be allowed to happen. The two features/settings stand in conflict with each other. I’m sure this is a problem for any users who have ‘Private’ logged-in only sites, operating the WooCommerce plugin. It’s a massive oversight I believe.
@shameemreza – I know you’ve been answering some similar topics on this and thank you for your work. I’d like to clarify that I don’t want to hide the Site Visibility setting, I don’t want it at all. Or at the very least, the Site Visibility setting cannot be allowed to override the WordPress Privacy settings. Can you please advise how we can keep our site Private for logged-in users and prevent the ‘Coming Soon’ page from appearing? I am happy to share some more helpful confidential information via email if that is possible, but I can’t share certain links/info here. If necessary, please feel free to add this incident report to the Github repository, as I do not have a login there.Regards,
DPL
- You must be logged in to reply to this topic.