Clarify order of operations for a child theme removing a filter of a parent theme. see #12695, see #12748

git-svn-id: http://svn.automattic.com/wordpress/trunk@13888 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
nacin 2010-03-30 12:55:08 +00:00
parent 33b86da7ce
commit 523b8a0846
1 changed files with 10 additions and 3 deletions

View File

@ -17,13 +17,20 @@
*
* Functions that are not pluggable (not wrapped in function_exists()) are instead attached
* to a filter or action hook. The hook can be removed by using remove_action() or
* remove_filter() and you can attach your own function to the hook. For example:
* remove_filter() and you can attach your own function to the hook.
*
* In this example, since both hooks are attached using the default priority (10), the first
* one attached (which would be the child theme) will run. We can remove the parent theme's
* hook only after it is attached, which means we need to wait until setting up the child theme:
*
* <code>
* remove_action( 'after_setup_theme', 'twentyten_setup' );
* add_action( 'after_setup_theme', 'my_child_theme_setup' );
* function my_child_theme_setup() {
* ...
* // We are replacing twentyten_setup() with my_child_theme_setup()
* remove_action( 'after_setup_theme', 'twentyten_setup' );
* // We are providing our own filter for excerpt_length (or using the unfiltered value)
* remove_filter( 'excerpt_length', 'twentyten_excerpt_length' );
* ...
* }
* </code>
*