by passing the entire template hierarchy

[Haluk Karamete]

Is there a way to by pass the great system known as the WordPress Template
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?

[Mikael Grön]

What are you trying to accomplish?

When I want to run pure code, for cron scripts and stuff, I usually do
something like this:

<?php

// in plugin or theme
add_action('get_header', function(){
if (strstr($_SERVER['REQUEST_URI'], '/cron/trigger_word')
{
// My code
exit;
}
});

?>

--
Regards
Mikael Grön

Post by Haluk Karamete
Is there a way to by pass the great system known as the WordPress Template
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Mikael Grön]

(sorry about the typo, coding in a gmail compose window is not recommended.)

--
Med vänliga hälsningar
Mikael Grön

Post by Mikael Grön
What are you trying to accomplish?
When I want to run pure code, for cron scripts and stuff, I usually do
<?php
// in plugin or theme
add_action('get_header', function(){
if (strstr($_SERVER['REQUEST_URI'], '/cron/trigger_word')
{
// My code
exit;
}
});
?>
--
Regards
Mikael Grön
Is there a way to by pass the great system known as the WordPress Template

Post by Haluk Karamete
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

[John Blackbourn]

It's a strange thing to need to do (you might want to re-think what
exactly it is you're doing) but it's simple enough:

add_filter( 'template_include', function( $template ) {
return locate_template( 'index.php' );
} );

Post by Haluk Karamete
Is there a way to by pass the great system known as the WordPress Template
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Haluk Karamete]

Thank you guys for your input.. I appreciate it.

John, I've built a new infustructure where things work differently and in
this infrustructure, the whole theme is done by a single index.php. And
that's always the case - which nullifies the need for the concept known as
template-hiearachy.

So there will never-ever be a need to say category.php.
I do not wish to get into the details here as to why I]ve built a framework
as such , and why I should or should not have done so etc.

Please note that this is not about overwriting the template hierarchy.

It's about totally by passing it
- which I have a feeling is not possible.

In the case of hooking into the "template_include" (or "template_redirect"
for that matter), it's an overwrite.

As you know, those hooks are run after wordpress core deployed the
template-hierarchy and in some cases 7 or 8 files have already been probed
for their existence. - which is exactly the process I'm trying to prevent
from taking place.

and as to the get_header option, Mikael, it's the same situation. By the
time, get_header hook sees the world, all the file_exists operations have
already been performed.

Let me put it this way, we all know index.php is the last resort in the
template-hierarchy.

Is there a hook that I can turn index.php being the first-resort?

Post by John Blackbourn
It's a strange thing to need to do (you might want to re-think what
add_filter( 'template_include', function( $template ) {
return locate_template( 'index.php' );
} );

Post by Haluk Karamete
Is there a way to by pass the great system known as the WordPress

Template

Post by Haluk Karamete
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

[John Blackbourn]

It sounds like you're trying to do something that doesn't belong as a
theme, but whatever. This should do the trick:

add_action( 'template_redirect', function() {
locate_template( 'index.php', true );
exit;
} );

Note that this will also affect feeds and things, so you might want to
add some `!is_feed()` logic in there if you still want feeds to work.

John

Post by Haluk Karamete
Thank you guys for your input.. I appreciate it.
John, I've built a new infustructure where things work differently and in
this infrustructure, the whole theme is done by a single index.php. And
that's always the case - which nullifies the need for the concept known as
template-hiearachy.
So there will never-ever be a need to say category.php.
I do not wish to get into the details here as to why I]ve built a framework
as such , and why I should or should not have done so etc.
Please note that this is not about overwriting the template hierarchy.
It's about totally by passing it
- which I have a feeling is not possible.
In the case of hooking into the "template_include" (or "template_redirect"
for that matter), it's an overwrite.
As you know, those hooks are run after wordpress core deployed the
template-hierarchy and in some cases 7 or 8 files have already been probed
for their existence. - which is exactly the process I'm trying to prevent
from taking place.
and as to the get_header option, Mikael, it's the same situation. By the
time, get_header hook sees the world, all the file_exists operations have
already been performed.
Let me put it this way, we all know index.php is the last resort in the
template-hierarchy.
Is there a hook that I can turn index.php being the first-resort?

Post by John Blackbourn
It's a strange thing to need to do (you might want to re-think what
add_filter( 'template_include', function( $template ) {
return locate_template( 'index.php' );
} );

Post by Haluk Karamete
Is there a way to by pass the great system known as the WordPress

Template

Post by Haluk Karamete
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Walter Ebert]

Hi,

you could try to use a custom front controller and use .htaccess to map
to that file, for example:

index2.php
<?php
require 'wp-load.php';
require get_template_directory() . '/index.php';


.htaccess
DirectoryIndex index2.php index.php index.html

Cheers,
Walter

Post by Haluk Karamete
Thank you guys for your input.. I appreciate it.
John, I've built a new infustructure where things work differently and in
this infrustructure, the whole theme is done by a single index.php. And
that's always the case - which nullifies the need for the concept known as
template-hiearachy.
So there will never-ever be a need to say category.php.
I do not wish to get into the details here as to why I]ve built a framework
as such , and why I should or should not have done so etc.
Please note that this is not about overwriting the template hierarchy.
It's about totally by passing it
- which I have a feeling is not possible.
In the case of hooking into the "template_include" (or "template_redirect"
for that matter), it's an overwrite.
As you know, those hooks are run after wordpress core deployed the
template-hierarchy and in some cases 7 or 8 files have already been probed
for their existence. - which is exactly the process I'm trying to prevent
from taking place.
and as to the get_header option, Mikael, it's the same situation. By the
time, get_header hook sees the world, all the file_exists operations have
already been performed.
Let me put it this way, we all know index.php is the last resort in the
template-hierarchy.
Is there a hook that I can turn index.php being the first-resort?

Post by John Blackbourn
It's a strange thing to need to do (you might want to re-think what
add_filter( 'template_include', function( $template ) {
return locate_template( 'index.php' );
} );

Post by Haluk Karamete
Is there a way to by pass the great system known as the WordPress

Template

Post by Haluk Karamete
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?
_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

_______________________________________________
wp-hackers mailing list
http://lists.automattic.com/mailman/listinfo/wp-hackers

[Shane Thompson]

Hi Haluk,

Although it is possible, as already described, I don't think it would be a
very good idea to circumvent this. If you must, template_include is
probably better for this than template_redirect, as template_redirect (my
understanding) is purely for doing redirects. ie. I want /courses/ to
redirect to /courses/medical so I would do this with template_redirect.

If you are trying to circumvent it for performance reasons, you're not
making much of a performance benefit at all. We can discuss ways to get the
best performance out of WP here, if that is what you are after.

Shane Thompson

Post by Haluk Karamete

Post by Haluk Karamete
Is there a way to by pass the great system known as the WordPress

Template

Post by Haluk Karamete
Hierarchy so that WordPress shoots the ball straight to the last resort
which is index.php?