WP_Privacy_Requests_Table::get_timestamp_as_date( int $timestamp ): string
- Since
- 4.9.6
- Source
wp-admin/includes/class-wp-privacy-requests-table.php:479
Compatibility
- WordPress
- since 4.9.6
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.
Parameters
$timestampint- Event timestamp.
Return value
string- Human readable date.
Performance profile
How much work a call to WP_Privacy_Requests_Table::get_timestamp_as_date() 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
- Scaling
- Constant
- Instructions
- 4–34
- Plugin surface
- None
- Called by
- 2
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 46.
Nothing here hands control to plugin code.
2 places in core call this, so the cost is paid more often than your own code shows.
What it touches
- hookthird-party callbacks
apply_filters()one call below WP_Privacy_Requests_Table::get_timestamp_as_date()
Further down the call graph this can also reach option, cache, serialize, query and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.
What one call costs · 3 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Privacy_Requests_Table::get_timestamp_as_date() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
empty($timestamp) | 4 | none |
!empty($timestamp) && $time_diff | 22 | time(), __(), human_time_diff(), sprintf() |
!empty($timestamp) && !$time_diff | 31–34 | time(), __(), __(), date_i18n(), __(), date_i18n(), sprintf() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 46 instructions, 4–34 executed per call, 3 branches. The work does not change between versions.
An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.
Uses · 3
- __()Retrieves the translation of $text.
- human_time_diff()Determines the difference between two timestamps.
- date_i18n()Retrieves the date in localized format, based on a sum of Unix timestamp and timezone offset in seconds.
Used by · 2
- WP_Privacy_Requests_Table::column_created_timestamp()Returns the markup for the Created timestamp column. Overridden by children.
- WP_Privacy_Requests_Table::column_status()Status column.
Source code
protected function get_timestamp_as_date( $timestamp ) { if ( empty( $timestamp ) ) { return ''; } $time_diff = time() - $timestamp; if ( $time_diff >= 0 && $time_diff < DAY_IN_SECONDS ) { /* translators: %s: Human-readable time difference. */ return sprintf( __( '%s ago' ), human_time_diff( $timestamp ) ); } return sprintf( /* translators: 1: privacy request date format, 2: privacy request time format. */ __( '%1$s at %2$s' ), /* translators: privacy request date format. See https://www.php.net/manual/en/datetime.format.php */ date_i18n( __( 'Y/m/d' ), $timestamp ), /* translators: privacy request time format. See https://www.php.net/manual/en/datetime.format.php */ date_i18n( __( 'g:i a' ), $timestamp ) ); }Changelog
Introduced in 4.9.6. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 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.