Here's my challenge:
I've got a design that has a lot of custom information for each post: Each post has its own stylesheet, its own image, plus two text elements (one a slogan and the other volume/issue information).
All this is in addition to the usual per-post stuff (content, title, excerpt), and all of it must be stored with each post so that, for example, when somebody views an archived post, he or she will see the correct image, the correct stylesheet, and so on. The blog will never show more than one post at a time.
What I understand so far is that I'm going to have to use custom fields, and I think I grasp that process. Create the fields, populate them, use one of the several relevant plugins to pull the information into the template.
What I don't understand is how â€“ on the blog's main page â€“ I can render that custom information in the various locations on the page (including the within the
<head>) that it needs to be.
Put differently, on an archived page, all this will be no problem, since a post-specific query happens in the URL and thus makes available post-specific information outside The Loop.
But on my site's main page, this can't happen, because until I get to The Loop, PHP/WP will have no way of knowing what post I want the custom information for.
Here are some possible solutions I've thought of:
1. Get the index page always to redirect to the permalink of the most recent post.
2. Expand The Loop to include, essentially, all of the page (beginning at the latest right before the
3. Somehow force the index.php or home.php template in my theme to recognize the "What one post are we dealing with here?" information that I pass fromâ€¦where?
#1 seems preferable to me by a good bit, because I imagine it could be done with a few lines of simple, clean PHP in the template. Sadly my PHP career is young, and I'm not sure where to begin with something like this. Is there any easy way with WP to test for the most recent post? Because then I think I could use the
template_redirect() thing (which I don't know a whole lot about just yet).
#2 just seems sloppy somehow, like it will cause more problems than it will solve. Just a gut feeling.
#3 seems like a nice solution, but I don't think there's a way to force a page to think it's a single-post page without calling a single post in the URL. Am I wrong?
Thanks for any direction and/or advice.