get_profile( $_GET['wpmdb-profile'] ); } else { $loaded_profile = $this->default_profile; } $is_default_profile = isset( $loaded_profile['default_profile'] ); $convert_exclude_revisions = false; $convert_post_type_selection = false; if ( ! $is_default_profile ) { if ( isset( $loaded_profile['exclude_revisions'] ) ) { $convert_exclude_revisions = true; } /* We used to provide users the option of selecting which post types they'd like to migrate. * We found that our wording for this functionality was a little confusing so we switched it to instead read "Exclude Post Types" * Once we made the switch we needed a way of inverting their saved post type selection to instead exclude the select post types. * This was required to make their select compatible with the new "exclude" wording. * This is easy enough for "push" and "export" saved profile as we know which post types exist on the local system and * can easily invert the selection. Pull saved profiles is a little trickier. * $this->maybe_update_profile() is used to update deprecated profile options to their new values. * At the time of page request $this->maybe_update_profile() cannot be used to update a pull profile as we don't know which * post types exist on the remote machine. As such we invert this selection later using the $convert_post_type_selection flag below. */ if ( isset( $loaded_profile['post_type_migrate_option'] ) && 'migrate_select_post_types' == $loaded_profile['post_type_migrate_option'] && 'pull' == $loaded_profile['action'] ) { $convert_post_type_selection = true; } $loaded_profile = $this->maybe_update_profile( $loaded_profile, $_GET['wpmdb-profile'] ); } if ( false == $is_default_profile ) { $loaded_profile = wp_parse_args( $loaded_profile, $this->default_profile ); } $loaded_profile = wp_parse_args( $loaded_profile, $this->checkbox_options ); $breadcrumbs_params = array( 'loaded_profile' => $loaded_profile, 'is_default_profile' => $is_default_profile, ); ?>
template( 'breadcrumbs', 'common', $breadcrumbs_params ); ?>
  • is_pro ) ? '' : ' style="display: none;"'; ?>
      • gzip() ) : ?>
    • template_part( array( 'pull_push_radio_buttons' ), $loaded_profile ); ?>

—
template_part( array( 'invalid_licence_warning' ) ); ?>

→
lock_url_find_replace_row ) ? ' readonly' : ''; ?> /> → lock_url_find_replace_row ) : ?>
→
lock_url_find_replace_row ) ? ' readonly' : ''; ?> /> → lock_url_find_replace_row || ( $this->lock_url_find_replace_row && $i != 1 ) ) : ?>
Add Row
New URL Missing — Please enter the protocol-relative URL of the remote website in the "New URL" field or remove the whole row entirely. If you are unsure of what this URL should be, please consult our documentation on find and replace fields.', 'wp-migrate-db' ); if ( $is_default_profile && $this->lock_url_find_replace_row ) { $new_url_missing_warning = __( 'New URL Missing — Please enter the protocol-relative URL of the remote website in the "New URL" field. If you are unsure of what this URL should be, please consult our documentation on find and replace fields.', 'wp-migrate-db' ); } ?>
New File Path Missing — Please enter the root file path of the remote website in the "New file path" field or remove the whole row entirely. If you are unsure of what the file path should be, please consult our documentation on find and replace fields.', 'wp-migrate-db' ), 'https://deliciousbrains.com/wp-migrate-db-pro/doc/find-and-replace/' ); ?>
template_part( array( 'select_tables', 'exclude_post_types' ), $loaded_profile ); ?>
  • WordPress Codex emphasizes that GUIDs should not be changed, this is limited to sites that are already live. If the site has never been live, we recommend replacing the GUIDs. For example, you may be developing a new site locally at dev.somedomain.com and want to migrate the site live to somedomain.com.', 'wp-migrate-db' ), 'http://codex.wordpress.org/Changing_The_Site_URL#Important_GUID_Note' ); ?>
    • template_part( array( 'exclude_post_revisions' ), $loaded_profile ); ?>
template_part( array( 'backup' ), $loaded_profile ); ?>
    settings['profiles'] as $profile_id => $profile ) { ++ $profile_id; ?>

".', 'wp-migrate-db' ); ?>

AFTER migration is complete, you will need to edit your local install\'s wp-config.php and change the "%1$s" variable to "".', 'wp-migrate-db' ), $wpdb->base_prefix, $wpdb->base_prefix ); ?>

base_prefix ); ?>

" and will ignore the migrated tables. So, AFTER migration is complete, you will need to edit your remote install\'s wp-config.php and change the "" variable to "%s".', 'wp-migrate-db' ), $wpdb->base_prefix ); ?>

mixed_case_table_name_warning( 'pull' ); ?>
mixed_case_table_name_warning( 'push' ); ?>

template( 'migrate-progress' ); ?>