• My test sites are behind a firewall, on a private network, and thus there’s no way to activate Jetpack there. So we use Jetpack’s development mode there.

    In order to keep things consistent between test and production, it kinda makes sense to leave “development mode” enabled even on production sites. That way, nobody will be tempted to use Jetpack components that haven’t been (and can’t be) tested.

    Are there any possible security issues involved with using development mode on public-facing production sites?

    https://wordpress.org/plugins/jetpack/

Viewing 1 replies (of 1 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    Feel free to use Jetpack’s Development mode on any site you want. It won’t create any issues. Development mode only removes the requirement to connect to WordPress.com (and the connection banners), and allows you to use the modules that do not require a connection.

Viewing 1 replies (of 1 total)

The topic ‘Issues with using "development" mode on production sites?’ is closed to new replies.