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 |
|---|---|
| 130 | </fieldset> |
| 131 | |
| 132 | |
| 133 | <fieldset id="<?php echo user_can_richedit() ? 'postdivrich' : 'postdiv'; ?>"> |
| 134 | <legend><?php _e('Page Content') ?> |
| 135 | |
| 136 | <?php if ( 'publish' == $post->post_status ) { ?> |
| 137 | <a href="<?php echo clean_url(get_permalink($post->ID)); ?>" style="position: absolute; right: 2em; margin-right: 19em; text-decoration: underline;" target="_blank"><?php _e('View »'); ?></a> |
| 138 | <?php } elseif ( 'edit' == $action ) { ?> |
| 139 | <a href="<?php echo clean_url(apply_filters('preview_post_link', add_query_arg('preview', 'true', get_permalink($post->ID)))); ?>" style="position: absolute; right: 2em; margin-right: 19em; text-decoration: underline;" target="_blank"><?php _e('Preview »'); ?></a> |
| 140 | <?php } ?> |
| 141 | </legend> |
| 142 | <?php the_editor($post->post_content); ?> |
| 143 | </fieldset> |
| 144 | |
| 145 | <p class="submit"> |
| 146 | <span id="autosave"></span> |
| 147 | <input name="save" type="submit" id="save" tabindex="3" value="<?php _e('Save and Continue Editing'); ?>" /> |
| 148 | <input type="submit" name="submit" value="<?php _e('Save') ?>" style="font-weight: bold;" tabindex="4" /> |