aaron13223

Here’s the whole process for better clarity:

We register an endpoint using register_rest_route() that acts as a webhook. (The function that adds this is hooked into the action rest_api_init)

When we recieve a request on that endpoint, we create an async action using as_enqueue_async_action()

We run WP Cron via the WP CLI that is managed by a systemd-timer. It basically runs at an interval to simply run the following command:
wp cron event run --due-now

And so action scheduler runs accordingly as well. The function run via this particular async action is this:

wp_trash_post( $order_id );

Also, thanks for the confirmation on simple_history/pause, we have implemented so I think it should “fix” our problem but I guess it would be good to sort out this “incorrect identifier” as well?

Please let me know if you would like me to mark this as solved. Thanks again for all your help!

I am adding some of the code snippets too, just in case.

Register Webhook:

$namespace = WPSC_NAMESPACE . '/' . WPSC_API_VERSION;
$route = 'checkout';

$args = array(
    'methods' => 'POST',
    'callback' => array($this, 'process_checkout'),
    'permission_callback' => array($this, 'validate_request'),
);

// Finally register our route 
register_rest_route( $namespace, $route, $args );

Enqueue Async Action:

as_enqueue_async_action(
    'wpsc_async_order_delete_order',  // $hook
    array('data' => $data,  // $args
    'wpsc_low',  // $group
    false, // $unique
    20
);

Hi @eskapism ,

Thanks for getting back so promptly. Here’s more details about the setup:

We use a custom plugin to register a rest route using register_rest_route()

Now when a request is made on that webhook, we use action scheduler to run the function as a background task using as_enqueue_async_action()

When the action scheduler queue runs the corresponding function, it simply calls wp_trash_post()

Let me know if there’s any more info you would require and thanks a lot for your help!

Hi @robertnextendweb ,

Thanks a lot for your help! nsl_{{provider_id}}_link_user action is what I was looking for.

I have one other question but it’s completely okay if you don’t answer since I understand custom code is out of scope.

Do you think wp_get_session_token() will work well in this context of the nsl action to get the session token of the user who just linked their social account?

Thanks again for your help!

Adding this in case someone ever needs it in the future:

function modify_nextend_register_message($translated_text, $text, $domain) {
    if ($text === 'Register For This Site') {
        return 'Custom message';
    }
    return $translated_text;
}
add_filter('gettext', 'modify_nextend_register_message', 20, 3);

For anyone that comes across this later. The templates do override if you put them in the correct folder just that you HAVE to clear object cache if you have it enabled. New templates do not appear unless you clear object cache like Redis. 😉

Hi Barry,

Thanks a lot for the detailed info!

I am sorry as I initially missed the WP-CLI part but now that I have read it, this is exactly what I was looking for!

I was already grouping tasks like this: abc-high, abc-medium, abc-low

I can now run specific groups of tasks with varying times with the systemd timer on the Server directly.

Thanks a lot for your help!

Hi Laszlo,

Thanks a lot for the quick turnaround. I am using the Free plugin and not the pro version. Could you please take a look at this link?

If you look closely, you will notice that the Google Login Button has a CLS Issue where it is hidden by default and as soon as the page fully loads, it comes into view.

The Button only looks like it’s “jumping” when I force the button to be displayed from the start using an external stylesheet. Let me know what you think or if you need anything else from me.

#nsl-custom-login-form-main .nsl-container{
    display: none;
}

The code above seems to be added and the display: block; is set with inline css – maybe that’s why?

Thanks again!

• This reply was modified 1 year ago by aaron13223.

Hey Kevin,

The url in the post editor is: https://vimeo.com/526338719/458ab0c2bc

This does embed normally when you’ve the plugin deactivated. Thanks again!