WP Insert重复创建文章问题：跨参数数据库迁移异常排查

Hey there, let's dig into why you're seeing duplicate posts and postmetas during your migration to WordPress. I've dealt with similar migration quirks before, so here are the most common culprits and actionable troubleshooting steps:

This is the #1 cause of duplicates. Let's rule this out first:

• Check if your migration function is hooked into WordPress events (like init or wp_loaded) multiple times—maybe via a plugin, theme functions file, or custom script.
• If you're running the migration via CLI or a web endpoint, make sure the script isn't being called repeatedly (e.g., accidental refreshes, cron jobs firing unexpectedly).
• Add a simple lock mechanism to prevent re-runs:

  // Check if migration has already run
  if (get_option('custom_migration_completed') === 'true') {
      return; // Exit early if done
  }
  
  // ... Your migration code here ...
  
  // Mark migration as completed once done
  update_option('custom_migration_completed', 'true');
  

If you're looping through source database records without tracking which ones you've already migrated, you'll end up re-creating posts every time the script runs. Fix this by:

• Adding a migrated flag column to your source database table, and marking records as migrated after successful insertion.
• Storing the source record's unique ID as a post meta in WordPress, then checking for its existence before inserting:

  $source_post_id = $source_record['id']; // Unique ID from your source DB
  // Check if this source post was already migrated
  $existing_post = get_posts([
      'meta_key' => '_source_post_unique_id',
      'meta_value' => $source_post_id,
      'post_type' => 'post',
      'posts_per_page' => 1,
      'fields' => 'ids'
  ]);
  
  if (!empty($existing_post)) {
      continue; // Skip this record—it's already migrated
  }
  
  // Proceed to create the post and postmeta
  $new_post_id = wp_insert_post([
      'post_title' => $source_record['title'],
      'post_content' => $source_record['content'],
      'post_status' => 'publish'
  ]);
  // Store the source ID to avoid duplicates later
  add_post_meta($new_post_id, '_source_post_unique_id', $source_post_id, true);
  

WordPress's save_post or wp_insert_post hooks can sometimes cause unintended side effects if plugins/themes are hooked into them. For example, a plugin might duplicate a post when it detects a new insertion.

• Temporarily disable all plugins and switch to a default theme (like Twenty Twenty-Four) then re-run the migration. If duplicates stop, you know a plugin/theme is the culprit.
• If you need to keep plugins active, temporarily unhook conflicting actions during migration:

  // Temporarily remove save_post hooks that might cause duplicates
  remove_all_actions('save_post');
  // ... Run your migration insertion code ...
  // Restore the hooks after migration
  add_action('save_post', 'your_original_save_post_function');
  

If your migration has error handling that retries failed inserts, it might re-create posts even if the initial insert actually succeeded (e.g., a network glitch made the script think it failed).

• Wrap your insertion logic in a try/catch block, and verify the post was created before proceeding.
• Check the WordPress posts table directly after a "failed" attempt to confirm if the post was actually inserted.

Start with the deduplication check and run lock—those fix 90% of duplicate migration issues. Let me know if you need help adapting any of these snippets to your specific code!

内容的提问来源于stack exchange，提问作者Alan Alegre da Cunha