peterle1984

Hello @zebaafiashama

Thank you for your prompt response and for looking into this with priority.

To assist your development team, I wanted to share the short-term fix we’ve successfully implemented on our end. This change has completely resolved the fatal errors and stabilized our site.

We confirmed the issue was an infinite recursion loop. The Social::publish_future_post() method was hooked to the wpsp_publish_future_post action, which is the same action the function itself triggers, causing the loop.

Here is the temporary fix we applied to the publish_future_post function in /wp-content/plugins/wp-scheduled-posts/includes/Social.php:

PHP

public function publish_future_post($post_id)
{
    // First, check if a share for this post is already scheduled to avoid duplicates.
    if (wp_next_scheduled('wpsp_publish_future_post', array($post_id))) {
        return;
    }

    // To prevent an infinite loop, we temporarily remove this function from its own hook.
    remove_action('wpsp_publish_future_post', array($this, 'publish_future_post'), 30);

    // Now, we can safely trigger the action that all other sharing functions listen to.
    do_action('wpsp_publish_future_post', $post_id);

    // Finally, we add the action back so it works for the next post.
    add_action('wpsp_publish_future_post', array($this, 'publish_future_post'), 30, 1);
}

This solution works by temporarily unhooking the function from the action it triggers, which effectively breaks the recursion. Our site has been running without any issues since this code was applied.

I hope this information is helpful for your debugging process.

Best regards,

Peter

• This reply was modified 10 months, 3 weeks ago by peterle1984.

Hi,

I got the message from Stripe that it is possible to offer other payment methods with Destination Charges.
It would be great if you did that.

https://stripe.com/docs/connect/destination-charges
https://stripe.com/docs/connect/custom-accounts

Manny Thank