Oh I see, I probably expressed myself badly. I didn't need that, in fact I never said I needed it, it's just I wanted it. I didn't need customizr hooks, I wanted them. I wanted to use the wordpress loop, and of course the global wp-query, 'cause I wanted to re-use customizr code to show the page. It's not just about displaying the content, it's about having also article class selectors etc., basically a structure of the displayed page coherent with the rest of the page (list of posts). To be honest I also wanted the title of the page written (and then hidden in css) because of that "google author/update fields issue".
Of course I saw your original reply, and I tried your code, that's why I said some posts above at least to wrap the content in an
<article>, maybe also adding some static class, to make it appear consistent with the rest of the page, or other page's contents (css).
Also what's the problem with the loop? Computationally basically null. The problem with query_posts, what's this big deal in this case? I use it outside the loop, I reset it before a new loop, It's inefficient as re-runs SQL queries (as stated in the codex), what that
$post = get_page_by_path( '/home' ) does if not a new sql query?
(And why not use
get_post then? Just to use the page slug instead of the id?)
For example, I think your code is useful if I wanted to append the content of a page inside another one (filtering the_content of the "container page"), and it will stay inside the <entry-content> .
There could be a better solution for what I wanted, without replicating the customizr code to show that content the way I wanted? I don't know, probably, and as I said I'm opened to that :D
Can your solution satisfy those (mine) requirements? I don't think so. Is it cheaper? I already told you I think that.
I'm sure interested in a way to achieve my same result without using query_posts to "replace for a while" the main query ('cause that's my aim). Could this be done with the pre_get_posts hook? I used it for different purposes, for example for displaying pages in the list of posts, but this is not the case...
Sometimes there are different ways to achieve the same result, in this case we proposed different codes to achieve similar result. People can choose what they want, if they want my result, then I think they need that code :P (until someone comes with a better one, of course :D), otherwise they can use your one (or use get_post), and just wrap the content in a selector to style it the way they want :).
Anyway.. pretty interesting topic :D eheh