prepare_items() to handle any data manipulation, then * finally call $yourInstance->display() to render the table to the page. * * Our theme for this list table is going to be movies. */ class TT_Example_List_Table extends WP_List_Table { /** ************************************************************************ * Normally we would be querying data from a database and manipulating that * for use in your list table. For this example, we're going to simplify it * slightly and create a pre-built array. Think of this as the data that might * be returned by $wpdb->query(). * * @var array **************************************************************************/ /*var $example_data = array( array( 'ID' => 1, 'IP' => '300', 'rating' => 'Clicks', 'director' => 'Last clicked on' ), array( 'ID' => 2, 'title' => 'Eyes Wide Shut', 'rating' => 'R', 'director' => 'Stanley Kubrick' ), array( 'ID' => 3, 'title' => 'Moulin Rouge!', 'rating' => 'PG-13', 'director' => 'Baz Luhrman' ), array( 'ID' => 4, 'title' => 'Snow White', 'rating' => 'G', 'director' => 'Walt Disney' ), array( 'ID' => 5, 'title' => 'Super 8', 'rating' => 'PG-13', 'director' => 'JJ Abrams' ), array( 'ID' => 6, 'title' => 'The Fountain', 'rating' => 'PG-13', 'director' => 'Darren Aronofsky' ), array( 'ID' => 7, 'title' => 'Watchmen', 'rating' => 'R', 'director' => 'Zach Snyder' ) );*/ /** ************************************************************************ * 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, $wpdb; //Set parent defaults parent::__construct( array( 'singular' => 'IP_ADDRESS', //singular name of the listed records 'plural' => 'IP_ADDRESS', //plural name of the listed records 'ajax' => false //does this table support ajax? ) ); /*$this->wpdb = $wpdb; $this->table_name = $this->wpdb->prefix."clickfraudmonitor"; //$example_data = "select * from ".$this->table_name." where IP_ADDRESS ='".$clickip."' and CLICK_TIMESTAMP >= '$clickdateimplode%' and BLOCKED = 1"; $sql = "select IP_ADDRESS, CLICK_TIMESTAMP from ".$this->table_name; $example_data = $this->wpdb->query($sql); //return $example_data; * */ } /** ************************************************************************ * 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 'title', 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 'title'. Instead, it * needs to handle everything else. * * For more detailed insight into how columns are handled, take a look at * 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 'IP_ADDRESS': case 'CLICK_TIMESTAMP': case 'CLICKCOUNT': case 'WHOIS': return $item[$column_name]; 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 'title'. 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 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 (movie title only) **************************************************************************/ function column_title($item){ //Build row actions $actions = array( 'edit' => sprintf('Edit',$_REQUEST['page'],'edit',$item['ID']), 'delete' => sprintf('Delete',$_REQUEST['page'],'delete',$item['ID']), ); //Return the title contents return sprintf('%1$s (id:%2$s)%3$s', /*$1%s*/ $item['IP_ADDRESS'], /*$2%s*/ $item['ID'], /*$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 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 (movie title only) **************************************************************************/ function column_cb($item){ return sprintf( '', /*$1%s*/ $this->_args['singular'], //Let's simply repurpose the table's singular label ("movie") /*$2%s*/ $item['IP_ADDRESS'] //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 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 'IP_ADDRESS' => 'IP Address', 'CLICKCOUNT' => 'Clicks', 'CLICK_TIMESTAMP' => 'Last click time', 'WHOIS' => 'Whois service', ); 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( 'IP_ADDRESS' => array('IP_ADDRESS',false), //true means it's already sorted //'CLICKCOUNT' => array('CLICKCOUNT',false), 'CLICK_TIMESTAMP' => array('CLICK_TIMESTAMP',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
elements, * so you will need to create those manually in order for bulk actions to function. * * @return array An associative array containing all the bulk actions: 'slugs'=>'Visible Titles' **************************************************************************/ function get_bulk_actions() { $actions = array( 'delete' => 'Delete' ); return $actions; } /** ************************************************************************ * Optional. You can handle your bulk actions anywhere or anyhow you prefer. * For this example package, we will handle it in the class to keep things * clean and organized. * * @see $this->prepare_items() **************************************************************************/ function process_bulk_action() { global $wpdb; $table_adclick = $wpdb->prefix."clickfraudmonitor"; //Detect when a bulk action is being triggered... if( 'delete'===$this->current_action() ) { //$strSQL = "DELETE * FROM" . $table_adclick; $strSQL = "DELETE FROM " . $table_adclick; $wpdb->query($strSQL); wp_die('IP adresses permanently deleted'); } } /** ************************************************************************ * REQUIRED! This is where you prepare your data for display. This method will * usually be used to query the database, sort and filter the data, and generally * get it ready to be displayed. At a minimum, we should set $this->items and * $this->set_pagination_args(), although the following properties and methods * are frequently interacted with here... * * @global WPDB $wpdb * @uses $this->_column_headers * @uses $this->items * @uses $this->get_columns() * @uses $this->get_sortable_columns() * @uses $this->get_pagenum() * @uses $this->set_pagination_args() * @param bool **************************************************************************/ function prepare_items($arg1) { global $wpdb; //This is used only if making any database queries /** * Name of the plugin table */ $table_adclick = $wpdb->prefix."clickfraudmonitor"; /** * First, lets decide how many records per page to show */ $per_page = 5; /** * 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(); /** * * arg1 show all ip addresses or only the blocked ones */ if ($arg1 == true) { $blocked = 'BLOCKED=1'; } else { $blocked = 'BLOCKED=1 OR BLOCKED=0'; } /** * 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. */ /* sort order */ $orderby = (!empty($_REQUEST['orderby'])) ? $_REQUEST['orderby'] : 'ID'; //If no sort, default to CLICK_TIMESTAMP $order = (!empty($_REQUEST['order'])) ? $_REQUEST['order'] : 'desc'; //If no sort, default to asc $sql = "select *,max(CLICK_TIMESTAMP) as CLICK_TIMESTAMP from ".$table_adclick." where " . $blocked . " group by IP_ADDRESS order by " . $orderby . " " . $order; //$sql = "SELECT ID, IP_ADDRESS, CLICK_TIMESTAMP, BLOCKED FROM" . $table_adclick; $result_qry = $wpdb->get_results($sql); $data = array(); /* build the result array */ if (!empty($result_qry)) { foreach ($result_qry as $row) { $ip = $row->IP_ADDRESS; $timestamp = $row->CLICK_TIMESTAMP; $blocked = $row->BLOCKED; //$query = "select * from " . $table_adclick . " where IP_ADDRESS ='" . $ip . "' and BLOCKED=1 order by CLICK_TIMESTAMP desc"; $query = "select * from " . $table_adclick . " where IP_ADDRESS ='" . $ip . "' and " . $blocked . " order by " . $orderby . " " . $order . ""; $results = $wpdb->get_results($query); $countresult = count($results); $data[] = array( 'ID' => $row->ID, 'IP_ADDRESS' => $row->IP_ADDRESS, 'CLICKCOUNT' => $countresult, 'CLICK_TIMESTAMP' => $timestamp, 'WHOIS' => 'Whois' ); } } /*$data = array( array( 'ID' => 1, 'IP_ADDRESS' => '192.123.12.03', 'CLICKCOUNT' => '5', 'CLICK_TIMESTAMP' => '23:12:23', 'WHOIS' => 'button' ), array( 'ID' => 2, 'IP_ADDRESS' => '192.123.12.08', 'CLICKCOUNT' => '6', 'CLICK_TIMESTAMP' => '23:12:23', 'WHOIS' => 'button' ) ); * */ //$data = $this->example_data; //$data=$wpdb->get_results($sql, ARRAY_A); /** * 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'] : 'IP_ADDRESS'; //If no sort, default to title $order = (!empty($_REQUEST['order'])) ? $_REQUEST['order'] : 'asc'; //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'); /*********************************************************************** * --------------------------------------------------------------------- * vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv * * In a real-world situation, this is where you would place your query. * * ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * --------------------------------------------------------------------- **********************************************************************/ /** * 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 ) ); } }