WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #18561, comment 76


Ignore:
Timestamp:
09/02/11 05:21:09 (3 years ago)
Author:
johnjamesjacoby
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18561, comment 76

    initial v1  
    77All of these are great ideas but only the template tag approach accurately solves this particular problem. Functions are easy for people to remember because they are native to PHP, unlike !WordPress action names which are native to !WordPress. Functions that start with "the_" are the first thing most people learn about !WordPress, so they are an easy addition in moderation. 
    88 
    9 The next best approach is having a set of ''theme specific'' actions fire at appropriate times in the page-load process. This is what most theme frameworks already attempt to do, so clearly it's popular and functional. !BuddyPress and !bbPress both already take this approach with their default themes, and having a standardized set of !WordPress '''core theme actions''' would be, in a word, awesome. 
     9The next best approach is having a set of ''theme specific'' actions fire at appropriate times in the page-load process. This is what most theme frameworks already attempt to do, so clearly it's popular and functional. !BuddyPress and bbPress both already take this approach with their default themes, and having a standardized set of !WordPress '''core theme actions''' would be, in a word, awesome. 
    1010 
    1111The ''get_template_part()'' and ''locate_template()'' tweaks also should make their way into !WordPress core. These enhancements along with a set of core theme actions are the plugin authors' holy grail to reliably piggy backing any !WordPress theme without jumping through flaming hoops of fearful incompatibility with thousands of awesome themes.