The user_status field isn’t used by core, so you could use it for your own purposes. Although there may be side effects if WP ever decides to reuse it in the future. The authenticate filter fires before the user is authenticated. You can hook into that filter and return a WP_Error object to prevent the … Read more
I figured out the answer. I needed to use the insert_user_meta filter, not an action hook. And then I ALSO needed a combo of get_user_meta (to get the old data) and $_POST to get the value being changed to. Putting it all together, here is my final code to find when a particular user_meta field … Read more
You are using the wrong meta key: update_user_meta( $user_id, ‘Save Posts’, $_POST[‘save_post_external’] ); update_user_meta( $user_id, ‘Save Posts’, $_POST[‘save_post_internal’] ); And that should be: update_user_meta( $user_id, ‘save_post_external’, $_POST[‘save_post_external’] ); update_user_meta( $user_id, ‘save_post_internal’, $_POST[‘save_post_internal’] );
Is there a smart way to meta_query so it matches just “IS, but not “TS-IS”? The WordPress meta query class (WP_Meta_Query), which among others, is used with the posts (WP_Query) and users (WP_User_Query) query classes, supports REGEXP (since WordPress 3.7) as the compare value, so you could use that with a RegEx (regular expresion) pattern … Read more
I just exported the live database, replaced all occurences of the live siteurl with the local one, and imported on my dev machine. Finding/replacing with a text editor breaks serialized data; you must change values with MySQL queries in phpmyadmin: UPDATE wp_options SET option_value = replace(option_value, ‘http://www.olddomain.com/’, ‘http://www.newdomain.com/’) WHERE option_name=”home” OR option_name=”siteurl”; UPDATE wp_posts SET … Read more
Maybe you need this: bp_displayed_user_id(). Also see playing with the user’s ID in different contexts in BuddyPress documentation.
First you can replace ‘posts_per_page’ => ‘10000000000’ with ‘posts_per_page’ => -1 to remove the limit. If you want to show the user rank, you can add a $rank counter in the foreach loop: $rank=0; // output the result: user, total postview count, latest post foreach ($output as $user){ $rank++; $profile = get_userdata($user[‘id’]); $query = get_posts( … Read more
If it’s information that logically belongs to a post/page – you store it in postmeta (with update_post_meta function). If it’s something that pertains to a user – usermeta table is for you. More still, there’s Settings API in case you have a plugin that needs to persist any settings. From your question it is somewhat … Read more
The obvious advantage of user meta is that you can use the WordPress API to record and retrieve these extra columns, without writing extra PHP classes or SQL queries. The wp_usermeta table is pretty well indexed, in fact, it uses one row per field (rather than one column if you use a custom table), and … Read more
Try this one with additional join on metadata SELECT u.ID, u.display_name FROM wp_users u LEFT JOIN wp_usermeta um1 ON u.ID = um1.user_id LEFT JOIN wp_usermeta um2 ON u.ID = um2.user_id WHERE um1.meta_value=”value1″ AND um1.meta_key = ‘key1’ AND um2.meta_key = ‘keyA’ AND um2.meta_value=”valueA” GROUP BY u.ID Also use group by