id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,focuses 50166,"A universal method to define a site's ""state""",joostdevalk,,"For all sorts of reasons, plugins need to figure out whether the current site is a ""live"" site versus a ""staging"" or ""development"" site. WooCommerce subscriptions solved this for themselves, as [https://docs.woocommerce.com/document/subscriptions-handles-staging-sites/ can be seen here]. Jetpack has ""[https://jetpack.com/support/staging-sites/ staging mode]"". We at Yoast partly fixed it and will need to fix it even better soon. Others _must_ run into this problem, where you don't want to show certain notices on a staging site that you do want to show on a live site. Would it be a good idea to set an option in the site settings, under Settings -> General, that toggles between three states: - development - staging - live Where ""live"" would obviously be the default. This would allow hosts that create staging sites to switch this toggle when they move a site to a staging environment etc. This way, Yoast SEO for instance could automatically block indexing of development and staging sites, and instead open up indexing on live sites. Other plugins like the Woo Subscriptions case above could also be solved much more uniformly.",feature request,closed,normal,,General,,normal,duplicate,,,