[wp-trac] [WordPress Trac] #18561: Better Way to Insert Things Below Individual Posts
WordPress Trac
wp-trac at lists.automattic.com
Fri Sep 2 17:10:46 UTC 2011
#18561: Better Way to Insert Things Below Individual Posts
-------------------------+------------------------------
Reporter: jane | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version: 3.2.1
Severity: minor | Resolution:
Keywords: |
-------------------------+------------------------------
Comment (by chipbennett):
Replying to [comment:87 aaroncampbell]:
> Replying to [comment:83 chipbennett]:
>
> I think that what you're talking about is actually an extension of
the_rest. If you look at my patch ( [attachment:18561.diff] and
[attachment:18561.twentyeleven.diff] ) it's basically just what you're
saying just only for ONE hook.
Looking at the patch, probably so (though I would recommend naming it
something like `wp_after_post()` or something equally semantic). The point
is, though, that we should '''first standardize''', and ''then patch''.
Adding pre/post-post hooks makes perfect sense - so much so, that the idea
will prompt addition of other equally useful hooks. Let's plan ahead for
that happening, so that we have an established location/naming convention.
> Coming up with a list of standard hooks would be great. If we start
requiring them in the theme directory maybe we won't need the
add_theme_support() calls.
Going this route makes it ''easier'' to add to the Theme Review guidelines
support for any such hooks. Rolling out support for these hooks would be
pretty easy, since 1) we could establish easy-to-follow instructions for
the Theme Review Guidelines, and 2) most commercial Themes implement
similar hooks anyway, and would very easily be able to support WP-core
variations of those hooks.
>
> Replying to [comment:85 brianlayman]:
> > Adding the extra hooks & tags won't break anything in current themes.
>
> While it won't break current themes, it WILL be difficult for plugins
that use them to transition, requiring them to have some way to fall back
for themes that DON'T have the new hooks.
The same is true for `wp_head()` and `wp_footer()`. As with these template
tags, the key is ''developer education'' of importance and proper
implementation.
Another benefit of first creating a standard nomenclature is that we can
begin developer education long before implementation happens.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/18561#comment:89>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list