the_modified_time( string $format = '' )
- Since
- 2.0.0
- Source
wp-includes/general-template.php:3003
Compatibility
- WordPress
- since 2.0.0
- 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
$formatstringoptional- Format to use for retrieving the time the post was modified. Accepts 'G', 'U', or PHP date format.
Defaults to the 'time_format' option.Default:''
Performance profile
How much work a call to the_modified_time() 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
- Heavy
- Scaling
- Constant
- Instructions
- 11
- Plugin surface
- 1 hook
- Called by
- 0
Reaches the database via get_post().
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5. The body compiles to 11.
Third-party callbacks on 'the_modified_time' run inside this call, and their cost is not bounded by anything here.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- hookthird-party callbacks
apply_filters()called directly - querycontent query
get_post()one call below the_modified_time() - optionoption read or write
get_option()one call below the_modified_time()
Further down the call graph this can also reach cache, serialize 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 · 1 distinct outcome
One number would be a lie: the work depends on which branch runs. These are every distinct cost the_modified_time() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 11 | get_the_modified_time(), apply_filters() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 11 instructions, 11 executed per call, 0 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.
Hooks and filters fired · 1
One hook fires while the_modified_time() runs, in this order:
- apply_filters( the_modified_time )filterline 3013 (+10 into the body)
Filters the localized time a post was last modified, for display.
Uses · 2
- apply_filters()Calls the callback functions that have been added to a filter hook.
- get_the_modified_time()Retrieves the time at which the post was last modified.
Source code
function the_modified_time( $format = '' ) { /** * Filters the localized time a post was last modified, for display. * * @since 2.0.0 * * @param string|false $get_the_modified_time The formatted time or false if no post is found. * @param string $format Format to use for retrieving the time the post * was modified. Accepts 'G', 'U', or PHP date format. */ echo apply_filters( 'the_modified_time', get_the_modified_time( $format ), $format );}Changelog
Introduced in 2.0.0. 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 6.9.7 tag, from
src/wp-includes/general-template.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.