15. Working with a staging environment
• It’s very important to disconnect Jetpack before
cloning or copying a site from the staging
environment to production or vice versa.
• If you lose your stats, don’t worry! Contact us
and we’ll fix things up for you!
16. Working with client sites
• There is one primary connection for each site (though other
users on a site can connect to WordPress.com as well). It’s
best to use your client’s WordPress.com account to connect
with. If they have a Gravatar or Akismet account, they have a
WordPress.com account.
• You can also use the Jetpack Dev mode:
define(
'JETPACK_DEV_DEBUG',
true);
wp-‐config.php:
in a plugin
add_filter(
'jetpack_development_mode',
'__return_true'
);
17. Working with client sites
• Control the modules that are activated by default:
function
my_function_only_stats()
{
return
array(
'stats'
);
}
add_filter(
'jetpack_get_default_modules',
'my_function_only_stats'
);
18. Working with client sites
• Never show a particular module:
function
function_only_stats
(
$modules
)
{
$return
=
array();
$return['stats']
=
$modules['stats'];
return
$return;
}
add_filter(
'jetpack_get_available_modules',
'function_only_stats'
);