wp_checkdate( int $month, int $day, int $year, string $source_date ): bool
- Since
- 3.5.0
- Source
wp-includes/functions.php:7385
Compatibility
- WordPress
- since 3.5.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
$monthint- Month number.
$dayint- Day number.
$yearint- Year number.
$source_datestring- The date to filter.
Return value
bool- True if valid date, false if not valid date.
Performance profile
How much work a call to wp_checkdate() 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
- 15
- Plugin surface
- 1 hook
- Called by
- 7
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. The body compiles to 15.
Third-party callbacks on 'wp_checkdate' run inside this call, and their cost is not bounded by anything here.
7 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()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_checkdate() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 15 | checkdate(), 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: 15 instructions, 15 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 wp_checkdate() runs, in this order:
- apply_filters( wp_checkdate )filterline 7394 (+9 into the body)
Filters whether the given date is valid for the Gregorian calendar.
Uses · 1
- apply_filters()Calls the callback functions that have been added to a filter hook.
Used by · 7
- WP_Customize_Manager::save()Handles customize_save WP Ajax request to save/update a changeset.
- WP_Date_Query::validate_date_values()Validates the given date_query values and triggers errors if something is not valid.
- WP_Query::parse_query()Parses a query string and sets query type booleans.
- _wp_translate_postdata()Renames `$_POST` data from form names to DB post columns.
- redirect_canonical()Redirects incoming links to the proper URL based on the site url.
- wp_resolve_post_date()Uses wp_checkdate to return a valid Gregorian-calendar value for post_date.
- wp_validate_site_data()Validates data for a site prior to inserting or updating in the database.
Source code
function wp_checkdate( $month, $day, $year, $source_date ) { /** * Filters whether the given date is valid for the Gregorian calendar. * * @since 3.5.0 * * @param bool $checkdate Whether the given date is valid. * @param string $source_date Date to check. */ return apply_filters( 'wp_checkdate', checkdate( $month, $day, $year ), $source_date );}Changelog
Introduced in 3.5.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.8.8 tag, from
src/wp-includes/functions.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.