Jack

Something like this:

<?php
// Define a function to retrieve data from the database
function get_data_from_database($query) {
    // Perform your database query here
    // ...

    // For the sake of this example, let's assume we fetched some data from the database
    $data = /* result of your database query */;

    return $data;
}

// Define a function to retrieve cached data or fetch it from the database
function get_data($query) {
    // Generate a unique cache key based on the query parameters
    $cache_key = 'data_query_' . md5(serialize($query));

    // Try to retrieve the data from the cache
    $cached_data = wp_cache_get($cache_key, 'my_cache_group');

    // If the data is found in the cache, return it
    if ($cached_data !== false) {
        return $cached_data;
    }

    // If the data is not in the cache, fetch it from the database
    $data = get_data_from_database($query);

    // Store the data in the cache
    wp_cache_set($cache_key, $data, 'my_cache_group', 3600);

    return $data;
}

// Example usage
$query1 = array('param1' => 'value1', 'param2' => 'value2');
$result1 = get_data($query1); // Fetches data from the database and caches it

$result2 = get_data($query1); // Retrieves data from the cache, avoiding the database query

$query2 = array('param1' => 'value1', 'param2' => 'value3');
$result3 = get_data($query2); // Fetches data from the database because the query parameters are different
?>

Hello,

Through the use of hooks I’ve removed the chance for my clients to be added to the wp_um_metadata table since clients aren’t listed anywhere.

function avoid_clients_directory_on_updated_usermeta($meta_id, $object_id, $meta_key, $_meta_value){
...
	if ( $is_client ) {

		remove_action( 'updated_user_meta', array( $member_directory_meta_this, 'on_update_usermeta' ), 10 );
	}
}


 

function avoid_clients_directory_on_added_usermeta($meta_id, $object_id, $meta_key, $_meta_value){

...
	if ( $is_client ) 

		remove_action( 'added_user_meta', array( $member_directory_meta_this, 'on_update_usermeta' ), 10 );


...

}

function avoid_client_members_for_directory() {

	add_action( 'updated_user_meta', 'avoid_clients_directory_on_updated_usermeta' , 9, 4 );
	add_action( 'added_user_meta', 'avoid_clients_directory_on_added_usermeta' , 9, 4 );
}
add_action( 'plugins_loaded', 'avoid_client_members_for_directory' );

And I’ve manual deleted client records from the table too which made it much smaller.
I think it made a small difference, however the query to list selects from the table wp_users which contains all users including clients which might be slowing down the query.


Thank you.

• This reply was modified 2 years, 11 months ago by Jack.

Is there anyway to speed up the database query to fetch the memebers?

I figured it out.

I had setup to run wp-cron.php every minute with wp cron disabled in wp-config.php. And I forgot to set the user I was running wp-cron.php as to the new daemon after migrating to a new stack, so it didn’t have permission to create and edit files.

The inconsistent behaviour was due to Action Scheduler either opting for WP CRON or using its Async Request instead randomly, Async Requests didn’t have the permission error because they were using the correct daemon to execute the jobs 

Thank you

Hello,

An update, I’ve found that this jobs only fail to write to fies when the action is executed with WP Cron instead of Async Request by Action Scheduler.
It seems since I turned off WP Cron using define('DISABLE_WP_CRON', true); and created a custom wp-cron.php caller, the actions called with WP Cron still work but cause this strange behaviour.

Is there any way to make use all Action Scheduler actions run using Async Request instead of WP Cron?

Thank you.

The outdated stripe gateway plugin seems to have cause the issue. It’s solved now.

Thank you.

A /v1/sources GET request is made to the Stripe webhook, but it doesn’t make the payment request.