WordPress+MemberPress环境下Stripe批量更新订阅价格技术咨询

我运营一个搭载MemberPress插件的WordPress站点，订阅服务通过Stripe完成支付。但MemberPress没有批量更新订阅价格的内置功能，Stripe后台也没有原生批量操作选项。我需要为Stripe中约5000个活跃订阅更新新价格，已编写的PHP脚本在Stripe测试模式下运行正常，但存在以下疑问：

1. 该脚本能否在WordPress单页执行中完成5000条订阅更新？存在哪些服务器性能或超时风险？
2. 手动更新WordPress/MemberPress中的会员价格以同步Stripe新价格是否安全合适？有无更优同步方案？

请帮忙评估我的代码并提供反馈建议，以下是带注释的脚本：

<?php
/*
This script is designed to update all Stripe subscriptions tied to a **specific price ID**.
It retrieves all subscriptions that are linked to an old price and updates them to a new price,
but only if both prices belong to the same product.
The update process is triggered by a URL parameter in the WordPress admin interface.

Steps:
1. Retrieve all subscriptions associated with the old price ID.
2. Verify that the old and new prices belong to the same product.
3. If they do, update those subscriptions to the new price.
4. Trigger the update via a URL parameter in the admin area.

*/

// Function to get the product ID for a specific price ID
function get_product_id_for_price($price_id, $api_key) {
    // Prepare cURL request to retrieve the price details
    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL, "https://api.stripe.com/v1/prices/$price_id");
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
    curl_setopt($ch, CURLOPT_USERPWD, $api_key . ":");

    // Execute the cURL request
    $response = curl_exec($ch);
    curl_close($ch);

    // Decode the response to get the price details
    $price_details = json_decode($response, true);

    // Return the product ID if the price exists, otherwise return null
    return isset($price_details['product']) ? $price_details['product'] : null;
}

// Function to get all subscriptions for a specific price ID
// This retrieves all subscriptions tied to a given price, supporting pagination if needed.
function get_all_subscriptions_for_price($price_id, $api_key) {
    $subscriptions = [];
    $has_more = true;
    $starting_after = null;

    // Loop through all pages of subscriptions until all are retrieved
    while ($has_more) {
        // Build the request URL, and include pagination if necessary
        $ch = curl_init();
        $url = "https://api.stripe.com/v1/subscriptions?price=$price_id&limit=100";

        if ($starting_after) {
            $url .= "&starting_after=$starting_after";
        }

        curl_setopt($ch, CURLOPT_URL, $url);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
        curl_setopt($ch, CURLOPT_USERPWD, $api_key . ":");

        // Execute the API request and store the result
        $response = curl_exec($ch);
        curl_close($ch);

        // Decode the JSON response into an array
        $result = json_decode($response, true);

        // If subscriptions are found, merge them with the existing list
        if (isset($result['data'])) {
            $subscriptions = array_merge($subscriptions, $result['data']);
            $has_more = $result['has_more'];
            $starting_after = end($result['data'])['id'];
        } else {
            // No more pages of subscriptions
            $has_more = false;
        }
    }

    return $subscriptions;
}

// Function to update all retrieved subscriptions to a new price
// This function takes an array of subscriptions and updates them to a new price ID.
function update_subscriptions_with_new_price($subscriptions, $new_price_id, $api_key) {
    foreach ($subscriptions as $subscription) {
        $subscription_id = $subscription['id'];
        $subscription_item_id = $subscription['items']['data'][0]['id'];

        // Prepare cURL request to update the subscription with the new price
        $ch = curl_init();
        curl_setopt($ch, CURLOPT_URL, "https://api.stripe.com/v1/subscriptions/$subscription_id");
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
        curl_setopt($ch, CURLOPT_USERPWD, $api_key . ":");
        curl_setopt($ch, CURLOPT_POST, true);
        curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
            'items[0][id]' => $subscription_item_id,
            'items[0][price]' => $new_price_id,
        ]));

        // Execute the cURL request
        $response = curl_exec($ch);
        curl_close($ch);

        // Decode the response and check for any errors
        $update_result = json_decode($response, true);
        if (isset($update_result['error'])) {
            echo "Error updating subscription ID $subscription_id: " . $update_result['error']['message'];
        } else {
            echo "Subscription ID $subscription_id updated successfully.\n";
        }
    }
}

// Function to update subscriptions for a specific price ID
// This retrieves all subscriptions linked to the old price and updates them to a new price if both prices belong to the same product.
function update_specific_subscriptions_for_price($product_id, $old_price_id, $new_price_id) {
    // Your Stripe secret API key to authenticate API requests
    $api_key = 'sk_test_xxxxxxxxxxxx';  // Stripe secret key

    // Step 1: Get the product IDs for the old and new prices
    $old_price_product_id = get_product_id_for_price($old_price_id, $api_key);
    $new_price_product_id = get_product_id_for_price($new_price_id, $api_key);

    // Step 2: Check if both prices belong to the specified product
    if ($old_price_product_id === $product_id && $new_price_product_id === $product_id) {
        echo "Both prices belong to the specified product. Proceeding with subscription updates.\n";

        // Step 3: Get all subscriptions tied to the old price ID
        $subscriptions = get_all_subscriptions_for_price($old_price_id, $api_key);

        // Step 4: If there are subscriptions, update them to the new price ID
        if (!empty($subscriptions)) {
            update_subscriptions_with_new_price($subscriptions, $new_price_id, $api_key);
        } else {
            echo "No subscriptions found for Price ID: $old_price_id\n";
        }
    } else {
        // Prices do not belong to the same product or specified product, do not proceed
        echo "Error: One or both of the price IDs do not belong to the specified product. No updates will be made.\n";
    }
}

// Example usage: Admin function to trigger subscription updates via a URL parameter
add_action('admin_init', function() {
    // The Product ID that both prices must belong to
    $product_id = 'prod_xxxxxxxxx';  // The actual product ID

    // The old Price ID that you want to update
    $old_price_id = 'price_xxxxxxxxx';    // The actual old price ID from Stripe

    // The new Price ID to which subscriptions should be updated
    $new_price_id = 'price_xxxxxxxxxx';    // The new price ID
    
    

    // Check if the update process is triggered by the URL parameter
    if (isset($_GET['trigger_subscription_update']) && $_GET['trigger_subscription_update'] === 'true') {
        // Run the function to update subscriptions tied to the old price ID
        update_specific_subscriptions_for_price($product_id, $old_price_id, $new_price_id);
    }
});
?>

疑问解答与代码反馈 #

1. 单页执行5000条订阅更新的可行性与风险 #

结论：几乎不可能在单页请求中完成，存在严重的超时和性能风险

• 超时风险：WordPress默认PHP执行超时通常在30-60秒，更新5000条订阅需要至少5000次Stripe API请求（单次请求耗时约0.5-1秒），总耗时至少40-80分钟，远超默认超时限制，脚本会中途中断。
• 服务器性能风险：
  • 持续的cURL请求会占用大量服务器带宽和CPU资源，可能导致站点其他请求响应缓慢甚至崩溃。
  • 一次性加载5000条订阅数据到数组中，会消耗大量PHP内存，容易触发内存溢出错误。
• Stripe API限制：Stripe默认请求速率限制为每秒100次，连续批量请求可能触发限流，导致部分更新失败。

2. 手动同步MemberPress价格的合理性与优化方案 #

手动更新MemberPress价格是安全的，但不是最优解

• 安全性：只要在MemberPress后台正确设置新价格（关联对应Stripe价格ID），不会直接影响已有的Stripe订阅（MemberPress不会自动修改Stripe侧订阅），但需确保新价格的Stripe ID与批量更新的ID一致，避免后续新订阅出现价格不一致问题。
• 更优同步方案：
  • 利用MemberPress钩子/API：批量更新Stripe订阅后，通过memberpress_subscription_updated钩子或官方API，批量更新WordPress侧对应的会员订阅记录价格，确保两边数据一致。
  • 定时任务同步：使用WordPress WP-Cron或服务器级Cron，定期检查Stripe与MemberPress的价格差异，自动修正不一致项。
  • Stripe Webhook同步：配置Stripe Webhook，当订阅价格更新时，自动通知WordPress并更新MemberPress对应的会员记录。

代码优化建议 #

1. 拆分为异步分批次任务

   • 使用WordPress后台任务队列（如WP Background Processing插件），每次处理50-100条订阅，分批次完成更新，避免超时。
   • 思路：先将所有订阅ID存入数据库，再通过定时任务每次取出部分ID执行更新，直至全部完成。

2. 替换为Stripe官方SDK

   • 用Stripe PHP SDK替代原生cURL，SDK会自动处理速率限制重试、错误处理和连接优化，降低代码出错概率。

3. 完善错误处理与日志

   • 不要用echo输出结果，改用WordPress的error_log()函数记录操作日志到服务器文件，方便后续排查问题。
   • 添加重试机制：Stripe API请求失败时（如网络波动、限流），自动重试2-3次。

4. 安全优化

   • 不要硬编码Stripe密钥，将其存入wp-config.php（如define('STRIPE_SECRET_KEY', 'sk_live_xxx');），避免密钥泄露。
   • 触发更新时增加权限验证，比如添加自定义密钥参数$_GET['secure_key'] === '你的安全密钥'，防止未授权访问。

5. 内存与性能优化

   • 不要一次性加载所有订阅到内存，处理完一页订阅后立即执行更新，再加载下一页，减少内存占用。
   • 关闭不必要的PHP错误输出，避免占用输出缓冲区。

内容的提问来源于stack exchange，提问作者Silveero