How to get user META values
-
I am attempting to change a plugin called WP SMS. The problem with this plugin is that you have to manually subscribe users to your list so that you can send SMS text messages.
WHAT I WANT TO DO:
Rather than manually sign people up for SMS, I’d like to populate the Subscribers list with actual WordPress users, or perhaps “CUSTOMERS” in which have registered through WOOCommerce.If I change the SQL query in the following code to WP_Prefix_users, it populates all WordPress users. Great, right? Except I am unable to get meta data attached to the user like “billing_phone” and “billing_first_name”. To access those, I have to query the code for WP_Prefix_usermeta. With how the plugin’s code is setup, populating the _usermeta generates 100+ rows, when I only need 4(amount of users), and display the meta_key and meta_value.
I will display the code I am working with along with a screenshot of the WordPress admin area and my current database.
<?php if ( ! class_exists( 'WP_List_Table' ) ) { require_once( ABSPATH . 'wp-admin/includes/class-wp-list-table.php' ); } class WP_SMS_Subscribers_List_Table extends WP_List_Table { var $data; function __construct() { global $status, $page, $wpdb, $table_prefix; //Set parent defaults parent::__construct( array( 'singular' => 'ID', //singular name of the listed records 'plural' => 'ID', //plural name of the listed records 'ajax' => false //does this table support ajax? ) ); $this->data = $wpdb->get_results( "SELECT * FROM <code>{$table_prefix}usermeta</code>", ARRAY_A ); } function column_default( $item, $column_name ) { switch ( $column_name ) { case 'meta_key': case 'meta_value': return $item[ $column_name ]; default: return print_r( $item, true ); //Show the whole array for troubleshooting purposes } } function column_name( $item ) { //Build row actions $actions = array( 'edit' => sprintf( '<a href="?page=%s&action=%s&ID=%s">' . __( 'Edit', 'wp-sms' ) . '</a>', $_REQUEST['page'], 'edit', $item['ID'] ), 'delete' => sprintf( '<a href="?page=%s&action=%s&ID=%s">' . __( 'Delete', 'wp-sms' ) . '</a>', $_REQUEST['page'], 'delete', $item['ID'] ), ); //Return the title contents return sprintf( '%1$s %3$s', /*$1%s*/ $item['name'], /*$2%s*/ $item['ID'], /*$2%s*/ $this->row_actions( $actions ) ); } function column_cb( $item ) { return sprintf( '<input type="checkbox" name="%1$s[]" value="%2$s" />', /*$1%s*/ $this->_args['singular'], //Let's simply repurpose the table's singular label ("movie") /*$2%s*/ $item['ID'] //The value of the checkbox should be the record's id ); } function get_columns() { $columns = array( 'cb' => '<input type="checkbox" />', //Render a checkbox instead of text 'meta_key' => __( 'Name', 'wp-sms' ), 'meta_value' => __( 'Mobile', 'wp-sms' ), ); return $columns; } function get_sortable_columns() { $sortable_columns = array( 'ID' => array( 'ID', true ), //true means it's already sorted 'name' => array( 'name', false ), //true means it's already sorted 'mobile' => array( 'mobile', false ) //true means it's already sorted ); return $sortable_columns; } function get_bulk_actions() { $actions = array( 'bulk_delete' => __( 'Delete', 'wp-sms' ) ); return $actions; } function process_bulk_action() { global $wpdb, $table_prefix; //Detect when a bulk action is being triggered... // Search action if ( isset( $_GET['s'] ) ) { $this->data = $wpdb->get_results( $wpdb->prepare( "SELECT * from <code>{$table_prefix}sms_subscribes</code> WHERE name LIKE %s OR mobile LIKE %s;", '%' . $wpdb->esc_like( $_GET['s'] ) . '%', '%' . $wpdb->esc_like( $_GET['s'] ) . '%' ), ARRAY_A ); } // Bulk delete action if ( 'bulk_delete' == $this->current_action() ) { foreach ( $_GET['id'] as $id ) { $wpdb->delete( $table_prefix . "sms_subscribes", array( 'ID' => $id ) ); } $this->data = $wpdb->get_results( "SELECT * FROM <code>{$table_prefix}sms_subscribes</code>", ARRAY_A ); echo '<div class="updated notice is-dismissible below-h2"><p>' . __( 'Items removed.', 'wp-sms' ) . '</p></div>'; } // Single delete action if ( 'delete' == $this->current_action() ) { $wpdb->delete( $table_prefix . "sms_subscribes", array( 'ID' => $_GET['ID'] ) ); $this->data = $wpdb->get_results( "SELECT * FROM <code>{$table_prefix}sms_subscribes</code>", ARRAY_A ); echo '<div class="updated notice is-dismissible below-h2"><p>' . __( 'Item removed.', 'wp-sms' ) . '</p></div>'; } } function prepare_items() { global $wpdb; //This is used only if making any database queries /** * First, lets decide how many records per page to show */ $per_page = 10; /** * REQUIRED. Now we need to define our column headers. This includes a complete * array of columns to be displayed (slugs & titles), a list of columns * to keep hidden, and a list of columns that are sortable. Each of these * can be defined in another method (as we've done here) before being * used to build the value for our _column_headers property. */ $columns = $this->get_columns(); $hidden = array(); $sortable = $this->get_sortable_columns(); /** * REQUIRED. Finally, we build an array to be used by the class for column * headers. The $this->_column_headers property takes an array which contains * 3 other arrays. One for all columns, one for hidden columns, and one * for sortable columns. */ $this->_column_headers = array( $columns, $hidden, $sortable ); /** * Optional. You can handle your bulk actions however you see fit. In this * case, we'll handle them within our package just to keep things clean. */ $this->process_bulk_action(); /** * Instead of querying a database, we're going to fetch the example data * property we created for use in this plugin. This makes this example * package slightly different than one you might build on your own. In * this example, we'll be using array manipulation to sort and paginate * our data. In a real-world implementation, you will probably want to * use sort and pagination data to build a custom query instead, as you'll * be able to use your precisely-queried data immediately. */ $data = $this->data; /** * This checks for sorting input and sorts the data in our array accordingly. * * In a real-world situation involving a database, you would probably want * to handle sorting by passing the 'orderby' and 'order' values directly * to a custom query. The returned data will be pre-sorted, and this array * sorting technique would be unnecessary. */ function usort_reorder( $a, $b ) { $orderby = ( ! empty( $_REQUEST['orderby'] ) ) ? $_REQUEST['orderby'] : 'date'; //If no sort, default to sender $order = ( ! empty( $_REQUEST['order'] ) ) ? $_REQUEST['order'] : 'desc'; //If no order, default to asc $result = strcmp( $a[ $orderby ], $b[ $orderby ] ); //Determine sort order return ( $order === 'asc' ) ? $result : - $result; //Send final sort direction to usort } usort( $data, 'usort_reorder' ); /** * REQUIRED for pagination. Let's figure out what page the user is currently * looking at. We'll need this later, so you should always include it in * your own package classes. */ $current_page = $this->get_pagenum(); /** * REQUIRED for pagination. Let's check how many items are in our data array. * In real-world use, this would be the total number of items in your database, * without filtering. We'll need this later, so you should always include it * in your own package classes. */ $total_items = count( $data ); /** * The WP_List_Table class does not handle pagination for us, so we need * to ensure that the data is trimmed to only the current page. We can use * array_slice() to */ $data = array_slice( $data, ( ( $current_page - 1 ) * $per_page ), $per_page ); /** * REQUIRED. Now we can add our *sorted* data to the items property, where * it can be used by the rest of the class. */ $this->items = $data; /** * REQUIRED. We also have to register our pagination options & calculations. */ $this->set_pagination_args( array( 'total_items' => $total_items, //WE have to calculate the total number of items 'per_page' => $per_page, //WE have to determine how many items to show on a page 'total_pages' => ceil( $total_items / $per_page ) //WE have to calculate the total number of pages ) ); } } ?>
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
- The topic ‘How to get user META values’ is closed to new replies.