I peeked into the WP_User_Query class and it supports a WP_Date_Query query on the user registration date. So we could use: $query = new WP_User_Query( $args ); or simply: $users = get_users( $args ); where: $args = [ ‘fields’ => ‘ID’, ‘number’ => 8, ‘date_query’ => [ [ ‘before’ => ‘359 days ago midnight’ ], … Read more
Your basic question is a pure SQL question. $count = $wpdb->get_var( ‘SELECT COUNT( comments.comment_ID ) FROM ‘. $wpdb->comments .’ as comments LEFT JOIN ‘.$wpdb->commentmeta.’ AS cmeta ON comments.comment_ID = cmeta.comment_id WHERE user_id = 1 AND comment_approved = “1” AND comment_type NOT IN (“pingback”, “trackback” ) AND cmeta.meta_key = “rating” AND cmeta.meta_value = 5′ ); I … Read more
Edited again to demonstrate adding and removing filters: Include these general functions in your functions.php. These are the filters you will invoke for the loops where you want to limit your query by these two meta values: function date_check_join( $join ) { global $wpdb; $join .= ” JOIN “.$wpdb->postmeta.” AS startdate ON (“.$wpdb->posts.”.ID = startdate.post_id … Read more
The whole bunch of code is to replicate the process, not to give the actual code. You have to figure out how your process can be meet up with this scenario. I commented on every possible line, please see the inline comments to get proper understanding. Step #1 First of all, the first portion of … Read more
Is it theoretically possible to have the following feature? Yes theoretically there are several Geo location API’s out there, the reliable ones you have to pay for, such as MaxMind. The latter part sounds strange, if you want the same content, then just use language files. If for some crazy reason you want to serve … Read more
If I understood you right… [A] Multi-Tax queries have the problem that they’re doing a JOIN of the meta table for every term. So imho it’s not the best idea to use the built in way. [B.1.a] I’d simply do a normal query with a one (main-)tax arg and then do the sorting depending on … Read more
I’d like to see what the actual generated SQL is that WP_Query is using, but for now. ( You can use http://wordpress.org/extend/plugins/debug-bar/ to easily view the SQL query ) Queries ordered by ‘random’ are inefficient. If you don’t need that remove it. If you do need a random order, consider removing it anyway and using … Read more
It looks like this section: AND (wptom_posts.post_status=”publish” OR wptom_posts.post_author = 1 AND wptom_posts.post_status=”private”) is not tied in at all to the two different query conditions… Perhaps the original code should be three conditions for part 1: array( ‘relation’ => ‘AND’, array( ‘taxonomy’ => ‘category’, ‘field’ => ‘slug’, ‘operator’ => ‘IN’), array( ‘taxonomy’ => ‘post_tag’, ‘field’ … Read more
So I added permissions for my $mydb user to have SELECT priviledges to my WordPress database. I then used this code to perform the JOIN: $sql=”SELECT * FROM `mydb`.`records` rec LEFT JOIN `wpdb`.`wp_users` usr ON rec.`mydb`=usr.`ID`”; $records = $mydb->get_results($sql, ARRAY_A); Worked great!
You are correct about the row not having much use outside of a two day threshold where a user doesn’t activate their account. I took a look at the codebase and can confirm there is no API function for removing a signup entry. The only code that removes a signup is the wpmu_validate_user_signup() function. It … Read more