Source View: customize_register

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: 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.

Source View

Line Code
2859            * will be reversed for two actions added at priority 10, resulting in
2860            * the core settings no longer being available as expected to themes/plugins.
2861            * So the following manually calls the method that registers the core
2862            * settings up front before doing the action.
2863            */
2864           remove_action( 'customize_register', array( $wp_customize, 'register_controls' ) );
2865           $wp_customize->register_controls();
2866
2867           /** This filter is documented in /wp-includes/class-wp-customize-manager.php */
2868           do_action( 'customize_register', $wp_customize );
2869      }
2870      $wp_customize->_publish_changeset_values( $changeset_post->ID ) ;
2871
2872      /*
2873       * Trash the changeset post if revisions are not enabled. Unpublished
2874       * changesets by default get garbage collected due to the auto-draft status.
2875       * When a changeset post is published, however, it would no longer get cleaned
2876       * out. Ths is a problem when the changeset posts are never displayed anywhere,
2877       * since they would just be endlessly piling up. So here we use the revisions