wp-admin/includes/class-wp-privacy-requests-table.php:502$itemWP_User_Request$column_namestringOne hook fires while WP_Privacy_Requests_Table::column_default() runs, in this order:
Fires for each custom column in the Application Passwords list table.
public function column_default( $item, $column_name ) { /** * Fires for each custom column of a specific request type in the Privacy Requests list table. * * Custom columns are registered using the {@see 'manage_export-personal-data_columns'} * and the {@see 'manage_erase-personal-data_columns'} filters. * * The dynamic portion of the hook name, `$this->screen->id`, refers to the ID given to the list table * according to which screen it's displayed on. * * Possible hook names include: * * - `manage_export-personal-data_custom_column` * - `manage_erase-personal-data_custom_column` * * @since 5.7.0 * * @param string $column_name The name of the column to display. * @param WP_User_Request $item The item being shown. */ do_action( "manage_{$this->screen->id}_custom_column", $column_name, $item ); }Introduced in 4.9.6. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
manage_{$this->screen->id}_custom_column action.from the docblocksrc/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.