Top ↑

Methods #Methods

• __construct — Sets the current data store object into `store->action` and initialises the object.
• bulk_delete — Bulk delete
• column_args — Serializes the argument of an action to render it in a human friendly format.
• column_log_entries — Prints the logs entries inline. We do so to avoid loading Javascript and other hacks to show it in a modal.
• column_schedule — Prints the scheduled date in a human friendly format.
• display_admin_notices — Renders admin notifications
• display_filter_by_status — Prints the available statuses so the user can click to filter.
• get_log_entry_html — Prints the logs entries inline. We do so to avoid loading Javascript and other hacks to show it in a modal.
• get_recurrence — Returns the recurrence of an action or 'Non-repeating'. The output is human readable.
• get_schedule_display_string — Get the scheduled date in a human friendly format.
• get_search_box_button_text — Get the text to display in the search box on the list table.
• human_interval — Convert an interval of seconds into a two part human friendly string.
• maybe_render_actions — Only display row actions for pending actions.
• prepare_items — {@inheritDoc}
• process_row_action — Implements the logic behind processing an action once an action link is clicked on the list table.
• recreate_tables — Force the data store schema updates.
• row_action_cancel — Implements the logic behind running an action. ActionScheduler_Abstract_ListTable validates the request and their parameters are valid.
• row_action_run — Implements the logic behind running an action. ActionScheduler_Abstract_ListTable validates the request and their parameters are valid.