prepare_items() to handle any data manipulation, then
* finally call $yourInstance->display() to render the table to the page.
*
*/
class wpp_list_unfonfirmed_email_table extends PB_WP_List_Table {
/** ************************************************************************
* REQUIRED. Set up a constructor that references the parent constructor. We
* use the parent reference to set some default configs.
***************************************************************************/
function __construct(){
global $status, $page;
global $wpdb;
//Set parent defaults
parent::__construct( array(
'singular' => 'user', //singular name of the listed records
'plural' => 'users', //plural name of the listed records
'ajax' => false //does this table support ajax?
) );
}
/** ************************************************************************
* Recommended. This method is called when the parent class can't find a method
* specifically build for a given column. Generally, it's recommended to include
* one method for each column you want to render, keeping your package class
* neat and organized. For example, if the class needs to process a column
* named 'username', it would first see if a method named $this->column_title()
* exists - if it does, that method will be used. If it doesn't, this one will
* be used. Generally, you should try to use custom column methods as much as
* possible.
*
* Since we have defined a column_title() method later on, this method doesn't
* need to concern itself with any column with a name of 'username'. Instead, it
* needs to handle everything else.
*
* For more detailed insight into how columns are handled, take a look at
* PB_WP_List_Table::single_row_columns()
*
* @param array $item A singular item (one full row's worth of data)
* @param array $column_name The name/slug of the column to be processed
* @return string Text or HTML to be placed inside the column
**************************************************************************/
function column_default($item, $column_name){
switch($column_name){
case 'email':
case 'registered':
return $item[$column_name];
case 'user-meta':
global $wpdb;
$sql_result = $wpdb->get_row( $wpdb->prepare( "SELECT * FROM " . $wpdb->base_prefix . "signups WHERE user_email = %s", $item['email'] ), ARRAY_A );
$user_meta = $sql_result['meta'];
$user_meta_content = '';
if( !empty( $user_meta ) ){
foreach( maybe_unserialize( $user_meta ) as $key => $value ){
if( $key != 'user_pass' ){
if ( is_array($value) ) $value = implode(',',$value);
$user_meta_content .= $key.':'.$value.' ';
}
}
}
return ''. __( 'show', 'profile-builder' ) .'';
default:
return print_r($item,true); //Show the whole array for troubleshooting purposes
}
}
/** ************************************************************************
* Recommended. This is a custom column method and is responsible for what
* is rendered in any column with a name/slug of 'username'. Every time the class
* needs to render a column, it first looks for a method named
* column_{$column_title} - if it exists, that method is run. If it doesn't
* exist, column_default() is called instead.
*
* This example also illustrates how to implement rollover actions. Actions
* should be an associative array formatted as 'slug'=>'link html' - and you
* will need to generate the URLs yourself. You could even ensure the links
*
*
* @see PB_WP_List_Table::::single_row_columns()
* @param array $item A singular item (one full row's worth of data)
* @return string Text to be placed inside the column
**************************************************************************/
function column_username($item){
$GRavatar = get_avatar( $item['email'], 32, '' );
//Build row actions
$actions = array(
'delete' => sprintf( '' . __( 'Delete', 'profile-builder' ) . '', wppb_curpageurl(), 'delete', $item['ID'] ),
'confirm' => sprintf( '' . __( 'Confirm Email', 'profile-builder' ) . '', wppb_curpageurl(), 'confirm', $item['ID'] ),
'resend' => sprintf( '' . __( 'Resend Activation Email', 'profile-builder' ) . '', wppb_curpageurl(), 'resend', $item['ID'] )
);
//Return the user row
return sprintf('%1$s %2$s %3$s',
/*$1%s*/ $GRavatar,
/*$2%s*/ $item['username'],
/*$3%s*/ $this->row_actions($actions)
);
}
/** ************************************************************************
* REQUIRED if displaying checkboxes or using bulk actions! The 'cb' column
* is given special treatment when columns are processed. It ALWAYS needs to
* have it's own method.
*
* @see PB_WP_List_Table::::single_row_columns()
* @param array $item A singular item (one full row's worth of data)
* @return string Text to be placed inside the column
**************************************************************************/
function column_cb($item){
return sprintf(
'',
/*$1%s*/ $this->_args['singular'], //Let's simply repurpose the table's singular label
/*$2%s*/ $item['ID'] //The value of the checkbox should be the record's id
);
}
/** ************************************************************************
* REQUIRED! This method dictates the table's columns and titles. This should
* return an array where the key is the column slug (and class) and the value
* is the column's title text. If you need a checkbox for bulk actions, refer
* to the $columns array below.
*
* The 'cb' column is treated differently than the rest. If including a checkbox
* column in your table you must create a column_cb() method. If you don't need
* bulk actions or checkboxes, simply leave the 'cb' entry out of your array.
*
* @see PB_WP_List_Table::::single_row_columns()
* @return array An associative array containing column information: 'slugs'=>'Visible Titles'
**************************************************************************/
function get_columns(){
$columns = array(
'cb' => '', //Render a checkbox instead of text
'username' => __( 'Username', 'profile-builder' ),
'email' => __( 'E-mail', 'profile-builder' ),
'registered' => __( 'Registered', 'profile-builder' ),
'user-meta' => __( 'User Meta', 'profile-builder' )
);
return $columns;
}
/** ************************************************************************
* Optional. If you want one or more columns to be sortable (ASC/DESC toggle),
* you will need to register it here. This should return an array where the
* key is the column that needs to be sortable, and the value is db column to
* sort by. Often, the key and value will be the same, but this is not always
* the case (as the value is a column name from the database, not the list table).
*
* This method merely defines which columns should be sortable and makes them
* clickable - it does not handle the actual sorting. You still need to detect
* the ORDERBY and ORDER querystring variables within prepare_items() and sort
* your data accordingly (usually by modifying your query).
*
* @return array An associative array containing all the columns that should be sortable: 'slugs'=>array('data_values',bool)
**************************************************************************/
function get_sortable_columns() {
$sortable_columns = array(
'username' => array('username',false), //true means it's already sorted
'email' => array('email',false),
'registered' => array('registered',false)
);
return $sortable_columns;
}
/** ************************************************************************
* Optional. If you need to include bulk actions in your list table, this is
* the place to define them. Bulk actions are an associative array in the format
* 'slug'=>'Visible Title'
*
* If this method returns an empty value, no bulk action will be rendered. If
* you specify any bulk actions, the bulk actions box will be rendered with
* the table automatically on display().
*
* Also note that list tables are not automatically wrapped in