WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )
apply_filters( "hook_name", "what_to_filter" )
.Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
Line | Code |
---|---|
1713 | /** |
1714 | * Filter whether the automatic updater should consider a filesystem location to be potentially |
1715 | * managed by a version control system. |
1716 | * |
1717 | * @since 3.7.0 |
1718 | * |
1719 | * @param bool $checkout Whether a VCS checkout was discovered at $context or ABSPATH, or anywhere higher. |
1720 | * @param string $context The filesystem context (a path) against which filesystem status should be checked. |
1721 | */ |
1722 | return apply_filters( 'automatic_updates_is_vcs_checkout', $checkout, $context ); |
1723 | } |
1724 |
|
1725 | /** |
1726 | * Tests to see if we can and should update a specific item. |
1727 | * |
1728 | * @since 3.7.0 |
1729 | * |
1730 | * @param string $type The type of update being checked: 'core', 'theme', 'plugin', 'translation'. |
1731 | * @param object $item The update offer. |