WooCommerce Order Status Hook

### Syntax

Here’s how the hook is used:

add_action( 'woocommerce_order_status_change', 'custom_order_status_change', 10, 4 );

function custom_order_status_change( $order_id, $old_status, $new_status, $order ) {
    // Your custom code here
    error_log( "Order #{$order_id} changed from {$old_status} to {$new_status}" );
}

### Parameters

1. **`$order_id`**: The ID of the order whose status changed.
2. **`$old_status`**: The previous status of the order.
3. **`$new_status`**: The new status of the order.
4. **`$order`**: The `WC_Order` object for the order.

### Example: Sending an Email on Status Change

add_action( 'woocommerce_order_status_change', 'send_email_on_status_change', 10, 4 );

function send_email_on_status_change( $order_id, $old_status, $new_status, $order ) {
    if ( $new_status === 'completed' ) {
        // Send an email when the order is marked as completed
        $to = $order->get_billing_email();
        $subject = 'Your order has been completed';
        $message = 'Hello, your order has been completed. Thank you for shopping with us!';
        
        wp_mail( $to, $subject, $message );
    }
}

### Use Case: External API Call

If you need to notify an external system:

add_action( 'woocommerce_order_status_change', 'notify_api_on_status_change', 10, 4 );

function notify_api_on_status_change( $order_id, $old_status, $new_status, $order ) {
    $api_url = 'https://example.com/api/orders/update-status';
    $response = wp_remote_post( $api_url, [
        'body' => json_encode( [
            'order_id'   => $order_id,
            'old_status' => $old_status,
            'new_status' => $new_status,
        ]),
        'headers' => [
            'Content-Type' => 'application/json',
        ],
    ]);
    
    if ( is_wp_error( $response ) ) {
        error_log( 'Failed to notify API: ' . $response->get_error_message() );
    }
}

### Notes

1. If you need to target a specific status transition (e.g., from "pending" to "completed"), consider using status-specific hooks like:

add_action( 'woocommerce_order_status_pending_to_completed', 'custom_function' );

2. Always test thoroughly, especially if interacting with external APIs, as errors can disrupt order processing.

Let me know if you'd like assistance implementing a specific use case!

### Steps

1. **Identify the Redirect Hook**
WooCommerce uses specific hooks or actions to handle redirects. For admin order actions, the redirect is usually managed through WordPress's admin redirect actions.

2. **Filter the Redirect URL**
You can use the `woocommerce_order_actions_redirect` filter or WordPress's `admin_post` hooks to control where the user is redirected after an action.

### Example Code

Here’s how you can modify the redirect behavior:

add_filter( 'woocommerce_order_actions_redirect', 'custom_order_action_redirect', 10, 2 );

function custom_order_action_redirect( $redirect_url, $order_id ) {
    // Check the action or conditions where you want to modify the redirect
    // For example, check if the order is being updated to a specific status
    $order = wc_get_order( $order_id );

    // Replace the redirect URL with a custom page or stay on the same page
    if ( $order ) {
        $redirect_url = remove_query_arg( [ 'message', 'action' ], wp_get_referer() ); // Stay on the same page
    }

    return $redirect_url;
}

### Stay on the Same Page After Status Change

WooCommerce might redirect users after certain admin actions. Use the following to stay on the same page:

add_filter( 'redirect_post_location', 'custom_redirect_after_order_status_change', 10, 2 );

function custom_redirect_after_order_status_change( $location, $post_id ) {
    $post_type = get_post_type( $post_id );

    // Check if the post type is 'shop_order'
    if ( $post_type === 'shop_order' ) {
        return remove_query_arg( [ 'message', 'action' ], wp_get_referer() );
    }

    return $location;
}

### Customize Admin Behavior for Specific Actions

If you need to customize behavior for a specific admin action (like bulk actions), you can use:

add_action( 'admin_action_edit', 'prevent_redirect_after_bulk_actions' );

function prevent_redirect_after_bulk_actions() {
    if ( isset( $_REQUEST['post_type'] ) && $_REQUEST['post_type'] === 'shop_order' ) {
        wp_safe_redirect( wp_get_referer() ); // Redirect to the previous page
        exit;
    }
}

### Explanation
1. **`woocommerce_order_actions_redirect`**:
– Filters the URL WooCommerce uses to redirect after order actions.
– You can modify this to point to a custom URL or stay on the same page.

2. **`redirect_post_location`**:
– Filters the redirection URL for all posts, including WooCommerce orders.

3. **`admin_action_edit`**:
– Handles custom admin actions like bulk edits or status changes.

By applying these filters, you can ensure users remain on the desired page after performing actions in WooCommerce admin. Let me know if you need additional customizations!

function custom_order_action_redirect( $redirect_url, $order_id ) {
// Check the action or conditions where you want to modify the redirect
// For example, check if the order is being updated to a specific status
$order = wc_get_order( $order_id );

// Replace the redirect URL with a custom page or stay on the same page
if ( $order ) {
$redirect_url = remove_query_arg( [ 'message', 'action' ], wp_get_referer() ); // Stay on the same page
}

return $redirect_url;
}
check above executer when user click apply button for order status change in wp admin

For the "Apply" button action in bulk updates or direct updates from the order edit page, you should ensure the correct hook is used. Let’s clarify the scenario and ensure it works:

### Revised Solution for Admin Apply Button (Bulk or Single Action)
Use the `redirect_post_location` hook instead, which is triggered for redirections after order actions, including bulk edits.

add_filter( 'redirect_post_location', 'custom_redirect_after_order_status_change', 10, 2 );

function custom_redirect_after_order_status_change( $location, $post_id ) {
    // Ensure we are dealing with an order
    if ( get_post_type( $post_id ) === 'shop_order' ) {
        // Stay on the same page by using wp_get_referer()
        return remove_query_arg( [ 'message', 'action' ], wp_get_referer() );
    }

    return $location; // For other post types, retain default behavior
}

### How It Works
1. **`redirect_post_location` Hook**
This is triggered whenever WordPress decides where to redirect after updating or saving a post (including WooCommerce orders). It works for the single and bulk status change actions.

2. **Condition for `shop_order`**
Ensures the modification applies only to WooCommerce orders (`shop_order` post type) and not other post types in the WordPress admin.

3. **Staying on the Same Page**
The `remove_query_arg()` function cleans unnecessary query parameters (like `message` and `action`) and redirects back to the referring page (`wp_get_referer()`).

### For Bulk Status Changes
If you want to modify the behavior for bulk actions specifically, you can use `admin_action_edit` to override redirection logic for bulk updates:

add_action( 'admin_action_edit', 'prevent_redirect_after_bulk_status_change' );

function prevent_redirect_after_bulk_status_change() {
    if ( isset( $_REQUEST['post_type'] ) && $_REQUEST['post_type'] === 'shop_order' ) {
        wp_safe_redirect( wp_get_referer() ); // Redirect to the previous page
        exit;
    }
}

### Steps to Test
1. Go to **WooCommerce > Orders** in the WordPress Admin.
2. Edit an order or apply a status change (either individually or in bulk).
3. After applying the change, confirm that the admin page does not redirect to the "All Orders" page but stays on the same page or the referring page.

### Debugging
If the behavior is not as expected:
1. Confirm the hook is applied by logging values:

error_log( 'Redirect URL: ' . $location );
   error_log( 'Post ID: ' . $post_id );

2. Check if the referring URL (`wp_get_referer()`) is being captured correctly.
3. Ensure no other plugin or theme code is overriding redirection behavior. Disable other plugins temporarily if necessary.

Let me know if you encounter any specific issues!

function custom_redirect_after_order_status_change( $location, $post_id ) {
// Ensure we are dealing with an order
if ( get_post_type( $post_id ) === 'shop_order' ) {
// Stay on the same page by using wp_get_referer()
return remove_query_arg( [ 'message', 'action' ], wp_get_referer() );
}

return $location; // For other post types, retain default behavior
}
Make sure above will execute only in wocommerce->orders when change order status by lickkng apply buttonnfrom bulk action

Here’s the updated code with added checks to make it work specifically for WooCommerce orders in the admin bulk actions:

### Updated Code

add_filter( 'redirect_post_location', 'custom_redirect_after_bulk_order_status_change', 10, 2 );

function custom_redirect_after_bulk_order_status_change( $location, $post_id ) {
    // Ensure this is triggered only in the WooCommerce Orders page and is a bulk action
    if ( is_admin() && isset( $_REQUEST['post_type'] ) && $_REQUEST['post_type'] === 'shop_order' ) {
        // Check if bulk action is applied
        if ( isset( $_REQUEST['bulk_edit'] ) || isset( $_REQUEST['action'] ) || isset( $_REQUEST['action2'] ) ) {
            return remove_query_arg( [ 'message', 'action', 'action2' ], wp_get_referer() ); // Stay on the same page
        }
    }

    return $location; // For other cases, retain default behavior
}

### How It Works

1. **Admin Context Check**
The `is_admin()` check ensures the code only executes in the WordPress admin area.

2. **Post Type Validation**
The `$_REQUEST['post_type'] === 'shop_order'` ensures this only applies to WooCommerce orders.

3. **Bulk Action Validation**
The presence of `$_REQUEST['bulk_edit']`, `$_REQUEST['action']`, or `$_REQUEST['action2']` confirms that a bulk action (like a status change) is being performed.

4. **Prevent Redirect to "All Orders"**
By using `wp_get_referer()`, we redirect back to the referring page (the current page) instead of the default "All Orders" page.

### Steps to Test

1. **Go to WooCommerce > Orders.**
Make sure you are on the orders listing page in the admin.

2. **Perform Bulk Status Change.**
– Select multiple orders using the checkboxes.
– Choose a new status from the "Bulk Actions" dropdown.
– Click the "Apply" button.

3. **Verify the Behavior.**
After clicking "Apply," you should stay on the same page (the orders listing) instead of being redirected to "All Orders."

### Debugging (Optional)

To debug or confirm the logic is working as intended, you can log some values:

error_log( 'Bulk Action: ' . ( $_REQUEST['action'] ?? 'none' ) );
error_log( 'Post Type: ' . ( $_REQUEST['post_type'] ?? 'none' ) );
error_log( 'Redirected to: ' . $location );

### Edge Cases

1. **Single Status Changes (Not Bulk)**
This code does not affect single status changes from the order edit page, as it specifically checks for bulk actions.

2. **Plugins Overriding Redirects**
If another plugin modifies the redirection behavior for bulk actions, ensure this filter has priority (you can adjust the priority from `10` to a lower number if necessary).

Let me know if further refinement is needed!

### Revised Solution

The redirect logic for bulk actions in WooCommerce admin can be influenced by both WordPress core and WooCommerce. Here's an updated implementation:

add_filter( 'redirect_post_location', 'custom_redirect_after_bulk_order_status_change', 10, 2 );

function custom_redirect_after_bulk_order_status_change( $location, $post_id ) {
    // Check if this is a WooCommerce bulk order status change
    if ( is_admin() && isset( $_REQUEST['post_type'] ) && $_REQUEST['post_type'] === 'shop_order' ) {
        // Check if the request includes bulk action parameters
        if ( isset( $_REQUEST['action'] ) && $_REQUEST['action'] !== '-1' ) {
            $bulk_action = $_REQUEST['action'];
        } elseif ( isset( $_REQUEST['action2'] ) && $_REQUEST['action2'] !== '-1' ) {
            $bulk_action = $_REQUEST['action2'];
        } else {
            $bulk_action = false;
        }

        // If a valid bulk action is detected, prevent redirection to "All Orders"
        if ( $bulk_action && strpos( $bulk_action, 'mark_' ) === 0 ) {
            // Stay on the current page after applying the bulk action
            return remove_query_arg( [ 'message', 'action', 'action2' ], wp_get_referer() );
        }
    }

    return $location; // For other cases, retain default behavior
}

### Key Points in the Code
1. **Bulk Action Validation**:
– The `action` and `action2` request variables are checked for a bulk action. If no action is selected, the value will be `-1`.
– WooCommerce bulk actions for changing order statuses typically start with `mark_`, such as `mark_completed`.

2. **Redirect to Referrer**:
– If a valid bulk order status change is detected, the `wp_get_referer()` function is used to redirect the user back to the referring page (same page).

3. **Fallback to Default Behavior**:
– If the conditions for bulk actions are not met, the default redirect location is returned.

### How to Test
1. Go to **WooCommerce > Orders** in the admin area.
2. Select multiple orders using the checkboxes.
3. Choose a bulk action like "Mark as Completed" from the dropdown.
4. Click the **Apply** button.
5. Confirm that you remain on the orders page instead of being redirected.

### Debugging Steps
If it’s still not working, add debugging logs to confirm which part of the code is executed:

error_log( 'Post Type: ' . ( $_REQUEST['post_type'] ?? 'none' ) );
error_log( 'Action: ' . ( $_REQUEST['action'] ?? 'none' ) );
error_log( 'Action2: ' . ( $_REQUEST['action2'] ?? 'none' ) );
error_log( 'Redirect URL: ' . $location );

Check the debug logs in `wp-content/debug.log` to see what values are being passed.

### Additional Notes
1. **Ensure Bulk Action Names Match**:
– WooCommerce uses bulk action names like `mark_completed`, `mark_processing`, etc. Ensure these match your actions.

2. **Plugin Conflicts**:
– Other plugins may modify the redirection behavior. Temporarily disable other plugins to test if this solution works.

Let me know how it behaves after this update! If needed, I can provide further debugging or explore alternative hooks.