search

Automattic / jetpack

Security, performance, marketing, and design tools — Jetpack is made by WordPress experts to make WP sites safer and faster, and help you grow your traffic.
https://jetpack.com/
Other
1.57k stars 793 forks source link

Admin: check that site is publicly accesible by WPCOM before activating certaing modules #5780

Open eliorivero opened 7 years ago

eliorivero commented 7 years ago

Follow up to https://github.com/Automattic/jetpack/pull/5609

  1. the code removed in that PR should be restored so the checking is performed, but,
  2. we should allow users to activate these modules and display a message telling user that it might not work as intended since the site is not publicly accesible by WordPress.com

The Sitemaps module does something similar (although it doesn't check that is publicly accessible by WPCOM) when the site is set to discourage search engines: it can be activated but it displays a message saying it will not work as intended until the site is accesible by search engines.

cc @zinigor @kraftbj

stale[bot] commented 6 years ago

This issue has been marked as stale. This happened because:

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

benlk commented 5 years ago

A note: Under Dashboard > Settings > Reading, checking "Discourage search engines from indexing this site" blocks the Elasticsearch indexer from running.

stale[bot] commented 4 years ago

This issue has been marked as stale. This happened because:

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.