Methods
1 to 14 of 14
- OIK_Clone_List_Table::column_post_title() – Display the post_title column
- OIK_Clone_List_Table::create_action_link() – Create an action link for the given action
- OIK_Clone_List_Table::determine_pagination() – Determine pagination parameters
- OIK_Clone_List_Table::get_bulk_actions() – Return the bulk actions supported
- OIK_Clone_List_Table::get_columns() – Return the columns to be displayed
- OIK_Clone_List_Table::load_items() – Load the items taking pagination into account
- OIK_Clone_List_Table::match_post() – Return an array of posts that match the given one
- OIK_Clone_List_Table::match_posts() – Starting with a list of $items we create a new list that combines the current items and the matched items Do we need to do this as OO code. Should it be a separate classs, or an interface?
- OIK_Clone_List_Table::prepare_items() – Prepare the contents to be displayed
- OIK_Clone_List_Table::record_pagination() – Set the pagination args based on what we found
- OIK_Clone_List_Table::reset_request_uri() – Ensure the pagination links don’t attempt to perform any actions
- OIK_Clone_List_Table::set_source() – Set the source to be used to access the data
- OIK_Clone_List_Table::trac30183() – Ultra foxed
- OIK_Clone_List_Table::__construct() – Construct an instance of OIK_Clone_List_Table
Extended by
API Letters: