Make get_template_part() accept multiple template names

[wjm]

This enhancement allows get_template_part() allows to pass several template names, to work in the same way as: locate_template()

so, you could call,

get_template_part( 'loop', array('category', 'taxonomy', 'archive') );

$names are passed by order of priority.

[wjm]

get_template_part() accepting multiple template names

[wjm]

forgot to mention:

$names can be pass a string or as an array, so it is backward compatible.

[nacin]

Seems sane, though too late for 3.0. It would be cleaner to simply case names as an array and use it in a single foreach.

[wjm]

Simplified version

[nacin]

I like this. Could you provide a basic case?

[nacin]

s/basic case/basic use case/

Another thought: If we do this for get_template_part(), we'd want to do it for get_footer(), get_header(), and get_sidebar() as well.

[wjm]

This is the first time i need to write something like this.
If this is not the case, let me know and i will do my best to write it again.

Allowing get_template_part() to take a second argument, allows theme designers to use "contextual" template parts.
Letting them extend themes based on different situations.
Working with a theme framework such as hybrid, which uses a function to get its context ( hybrid_get_context() will retrieve a list of contexts
example

array (
    [0] => archive
    [1] => taxonomy
    [2] => category
    [3] => category-bananas
)

so by calling ( get_template_part( array_reverse( hybrid_get_context() ) ) )
this way it is possible to call 'loop-category-bananas.php' just by creating the template file, but if that file is not present, then 'loop-category.php' is called, and so on.

Letting theme designers focus on creating the files rather worrying about modifying the code.

this change can also be applied to get_footer(), get_header(), get_sidebar()
letting theme designer create featured footers, headers, sidebars for certain situations.

[nacin]

I like this. The only thing is that we'd be looking at a good number of file_exists checks there to traverse the entire context tree. I suppose if we can patch all four functions, we can go from there.

[wjm]

implements get_template_part() in get_header(), get_footer() and get_sidebar()

[wjm]

Cache system + require_once

[wjm]

Changes made to the last patch.

require_once argument added to get_template_part(),
this is set to true to get_header(), get_footer() and get_sidebar()

A cache listing the template files has been created, which I hope speeds things up avoiding to run file_exists().
It also reads template subdirectories, only on demand (not commonly used buy it was possible to include a template using a / in its slug or name).

If someone can benchmark this, but all the code was made with speed in mind.

[wjm]

This removes the need to add an action

[scribu]

Replying to wjm:

Allowing get_template_part() to take a second argument, allows theme designers to use "contextual" template parts.
Letting them extend themes based on different situations.

I think a better way to go about this would be #12877.

Suggest closing as duplicate.

[SergeyBiryukov]

#25558 was marked as a duplicate.

[chriscct7]

Related #14310