WP_Privacy_Requests_Table::column_default( WP_User_Request $item, string $column_name )

Compatibility

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$itemWP_User_Request

Item being shown.

$column_namestring

Name of column being shown.

Performance profile

How much work a call to WP_Privacy_Requests_Table::column_default() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class

Trivial

Touches nothing outside its own arguments.

Scaling

Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions

13

Executed per call on PHP 8.5. The body compiles to 13.

Plugin surface

1 hook

Third-party callbacks on 'manage_{$this->screen->id}_custom_column' run inside this call, and their cost is not bounded by anything here.

Called by

0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

• hookthird-party callbacksdo_action()called directly

What one call costs · 1 distinct outcome

One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Privacy_Requests_Table::column_default() can have, taken from its control-flow graph on PHP 8.5.

Hooks and filters fired · 1

One hook fires while WP_Privacy_Requests_Table::column_default() runs, in this order:

1. 1
   do_action( manage_{$this->screen->id}_custom_column )actionline 522 (+20 into the body)

   Fires for each custom column in the Application Passwords list table.

Uses · 1

• do_action()Calls the callback functions that have been added to an action hook.

Source code

View on Trac ↗View on GitHub ↗

502	public function column_default( $item, $column_name ) {503		/**504		 * Fires for each custom column of a specific request type in the Privacy Requests list table.505		 *506		 * Custom columns are registered using the {@see 'manage_export-personal-data_columns'}507		 * and the {@see 'manage_erase-personal-data_columns'} filters.508		 *509		 * The dynamic portion of the hook name, `$this->screen->id`, refers to the ID given to the list table510		 * according to which screen it's displayed on.511		 *512		 * Possible hook names include:513		 *514		 *  - `manage_export-personal-data_custom_column`515		 *  - `manage_erase-personal-data_custom_column`516		 *517		 * @since 5.7.0518		 *519		 * @param string          $column_name The name of the column to display.520		 * @param WP_User_Request $item        The item being shown.521		 */522		do_action( "manage_{$this->screen->id}_custom_column", $column_name, $item );523	}

Changelog

Introduced in 4.9.6. Unchanged from 6.7.7 through 7.1.0.

1. 6.7.7
2. 6.8.8
3. 6.9.7
4. 7.0.4
5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data

Generated from the wordpress-develop 6.8.8 tag, from src/wp-admin/includes/class-wp-privacy-requests-table.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.

Corrections

Something wrong on this page? Report it and it gets fixed in the next regeneration.