New to the community? Start here

Best filter for Jetpack support?

Howdy!

I’m from Automattic, the team behind Jetpack. I’m working with a mutual user with a large multisite using Cloner to clone sites.

When cloning a site with an active Jetpack connection, Cloner is also copying over the “unique” bits in the database that will cause issues for both sites and their relationship with WordPress.com.

Specifically, for both sites to operate as expected, we need to not clone the jetpack_private_options row in the options table. On the original site, it contains an array of the unique values for the site. The lack of one on the destination site will simply require the user to connect to Jetpack, leaving the rest of the settings as set from the cloned site.

Any suggestions on the best place I can suggest to the user to hook into would be appreciated. If possible, it would be great if this could be added as an integration as well.

Thanks!

Thu, 25 Feb 2016 19:34:14
  • Ignacio
    • HummingBird

    Hi @kraftbj.

    There’s already a filter for this kind of situations in Cloner:

    add_filter( 'wpmudev_copier_exclude_settings', 'cloner_jetpack_exclude_settings' );
    
if ( ! function_exists( 'cloner_jetpack_exclude_settings' ) ) {
    
function cloner_jetpack_exclude_settings( $exclude_settings ) {
    
$exclude_settings[] = 'jetpack_private_options';
    
return $exclude_settings;
    
}
    
}

    That should work fine. I’ll add it for next Cloner release too.

    Regards.

    Ignacio.