Blade templates need to be compiled to PHP and then output, rather than included directly like a standard WordPress template file. So, if everything is working except you’re seeing the raw Blade code rather than the rendered template, then you probably just need to use the template() function to compile your template and then echo the result.
Try something like echo template(get_404_template()); instead of require get_404_template();.
Hi @mmirus
awesome, we’re almost there. Now it renders the 404 template but from there I don’t have the variables passed by the App.php controller.
I placed @debug in the 404 template and indeed it prints nothing.
You know why?
Thanks!
When you call a Blade template using template(get_404_template()) you need to pass variables too it directly; it won’t automatically inherit them from context. i.e. template(get_404_template(), ['variable_name' => 'some data']).
Is there a reason you can’t do the same thing with pre_get_posts and just turn all post requests into 404s before you get to template_redirect? i.e.:
Yes, I could use pre_get_posts but your code catch all single (including custom post type single), while I need to catch only “post” single (not custom post types). How can do it?
Also, should I add this steps?
// 2. Fix HTML title
add_action( 'wp_title', function () {
return '404: Not Found';
}, 9999 );
// 3. Throw 404
status_header( 404 );
nocache_headers();
// 5. Stop execution
exit;
My code is just an example to get you started, not a literal replacement. There are a lot of conditionals on the $query object that you can check to make sure it only runs on the correct post type: Class Reference/WP Query « WordPress Codex
My first step is to check if my conditional is working by adding some code that I know with have an effect I’ll see, like die("I work!"), to see if it’s my conditional that’s not working, or the actual effect I’m shooting for (in your case forcing a 404) not firing.
Hi @alwaysblank, tried your code and it prints I work! on any single post types, while I need it worked just for default single post (not custom post types)
I think the conditional $query->is_single catches any single and I can’t find the one I need…
Maybe try var_dump($query) before die() and then load one page with the standard post type and one with a custom post type? That way you should be able to find a property of $query that you can use in combination with the code that you got from @alwaysblank to target only the standard post type.
My bad. $query doesn’t seem to hold any post data that can be easily used to determine the post type when called using the pre_get_posts filter.
But what if you use the filter template_include instead of the action template_redirect that you used in your original post? As taken from the documentation for template redirect: “Loading a different template is not a good use of this action hook.”
Something like:
add_action('template_include', function($template) {
if (is_singular('post')) {
global $wp_query;
$wp_query->set_404();
// In case you need to make sure that `have_posts()` return false.
// Maybe there's a reset function on WP_Query but I couldn't find one.
$wp_query->post_count = 0;
$wp_query->posts = [];
$wp_query->post = false;
status_header(404);
$template = get_404_template();
}
return $template;
});
Wow @folbert it seems work well! It renders the Blade template and I have also the variables passed by App.php controller. Awesome.
Just some details to understand.
Basing on this article, he adds add_action(wp_title)... and nocache_headers(); and exit at the end. You didn’t add them in your code. Are they unnecessary?
How can I return 404 also for standard post archive? In general I need to return 404 for all URL related to standard post
Title - If the <title> for the 404-page that you get is not what you want, use the code from the article. If you want to use the same custom title for all your 404 pages, put the code outside of my example code.
nocache_headers() - since WPs execution will continue as normal, I assume that WP core will take care of applying that function if needed.
exit - what happens if you add exit anywhere in the code?
Not to sound harsh but that is more a general WP question than related to Sage so to paraphrase Neo: "Where you go from here, is a choice I leave to you. "
Placing exit before the return I get browser 404 page (no WP template loaded), while placing it after the return it works identical (it loads the WP 404 template).
