Languages: English • Español • Français • Loop in Action 日本語 中文(简体) • Українська • Русский • বাংলা • Italiano • (Add your language)
"The Loop" è l'elemento principale di WordPress. Useremo il Loop nel nostro template files per visualizzare i Posts ai visitatori. Potremmo creare Templates senza il Loop, ma protremmo visualizzare solo i dati del Post.
Prima che il Loop entri in azione, WordPress verifica che tutti i Files di cui esso ha bisogno siano presenti. Allora come definito dal blog administrator, raccoglie le impostazioni predefinite dal Database. Questo include il numero dei posts, da visualizzare per pagina, l'abilitazione o meno dei commenti, e molto altro. Una volta terminate queste operazioni di default, WordPress controlla per vedere cosa l'utente ha richiesto. Questa informazione viene utilizzata per determinare quali post recuperare dal database. Se l'utente non chiede uno specifico Post, Category, Page, o Date, WordPress usa i valori predefiniti precedentemente raccolti, per determinare quali Posts recuperare per l'utente. Per esempio, se il blog administrator è impostato per visualizzare 5 Posts per pagina in Administration > Settings > Reading, allora WordPress prenderà dal Database i 5 Posts più recenti. Se l'utente richiede uno specifico Post, Category, Page, o Date, allora WordPress userà quella informazione specifica quale post(s) da prendere dal database.
Dopo che tutte queste operazioni sono svolte, WordPress si connette al Database, recupera le informazioni richieste, è memorizza il risultato in una variabile. Il Loop usa i valori di questa variabile per visualizzare il nostro Templates.
Di default, se il visitatore non seleziona uno specifico Post, Page, Category, o Date, WordPress usa index.php per visualizzare ogni cosa. Per la prima parte di questa discussione sul Loop ci focalizzeremo soltando su index.php, e la visualizzazione standard del blog. Successivamente, una volta compreso come lavora il Loop, esamineremo come funziona in altri template files.
Il seguente è un semplice Index file (index.php), che visualizza il contenuto (e solo il contenuto) di ogni Post, in base alle condizioni usate per preparare il Loop. Questo esempio mostra quanto piccolo è il codice necessario per il Loop.
<?php
get_header();
if (have_posts()) :
while (have_posts()) :
the_post();
the_content();
endwhile;
endif;
get_sidebar();
get_footer();
?>
The following is a step-by-step look at the default usage of the Loop that comes with the default and classic theme in the standard installation of WordPress v1.5.
All'inizio del Template File index.php, di default, si trova il codice di avvio per The Loop.
<?php if (have_posts()) : ?> <?php while (have_posts()) : the_post(); ?>
La funzione have_posts() controlla semplicemente l'elemento successivo dei Posts recuperati. Internamente, tutto questo si basa su un contatore di Posts, che viene confrontato con il numero torale di Posts recuperati. La funzione the_post() quindi recupera il post successivo e aggiorna il contatore dei post interni. Alla prossima valutazione di have_posts() nel while clause, if another item is present, the while loop body is executed again for the next post. When the posts collection is exhausted (the posts counter matches the total number of posts), the while loop ends and The Loop moves on to whatever instructions it has beyond the while statement, still within the if test. For example, the if might have an else clause with statements to be executed if the posts collection did not contain any data in the first place.
La funzione the_post() takes the current item in the collection of posts and makes it available for use inside this iteration of The Loop. Without the_post(), many of the Template Tags used in your theme would not work.
Una volta che i dati del Post sono disponibili, il Template lo converte in HTML e lo spedisce al visitatore.
The following template tags get the current post's title, the time it was posted, and who posted it.
<h2 id="post-<?php the_ID(); ?>">
<a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>">
<?php the_title(); ?></a></h2>
<small><?php the_time('F jS, Y') ?> <!-- by <?php the_author() ?> --></small>
The the_content() template tag fetches the content of the post, filters it, and then displays it. This is the meat and potatoes of each pass through The Loop:
<div class="entry">
<?php the_content('Read the rest of this entry »'); ?>
</div>
As the the_content() documentation states, the <!--more--> quicktag is used to specify an excerpt for the_content() to display on multi-post pages. The string passed to the_content() is used for the "Read More" link after the excerpt. For more about excerpts, the <!--more--> quicktag, and the "Read More" link see Template Tags/the_content and Customizing the Read More.
The post meta data section is located beneath each post's content in the index.php template file, and is used to display more information about the post, such as the categories, date, and comment information. By placing the edit_post_link() template tag function, logged in users of sufficient privilege (or the post's author) will also see an "Edit This" link.
<p class="postmetadata">
Posted in <?php the_category(', ') ?>
<strong>|</strong>
<?php edit_post_link('Edit','','<strong>|</strong>'); ?>
<?php comments_popup_link('No Comments »', '1 Comment »', '% Comments »'); ?></p>
If commenting is enabled, or if the post has comments, the comments_popup_link() template tag will display a link to the comments. If you're using the comments popup window, this link will open the comments window; otherwise it will jump right to this post's comments.
If the visitor is viewing an index of posts (i.e.: more than one post in The Loop), the comments_popup_link() link will take the reader to this post's individual page.
The trackback_rdf template tag's function is to output machine-readable code used for trackback auto-discovery.
<!-- <?php trackback_rdf(); ?> -->
Note: The trackback_rdf() tag is intentionally used within an HTML comment; it is not being "turned off". The reason for this is that, otherwise, RDF breaks validation in non-XML documents, and in XHTML documents it is parsed incorrectly by most browsers.
The following ends The Loop. After this, the various post-related template tags will not work as expected (or if they do, they will use the last post from The Loop). This means, that if you need to use a template tag that works within The Loop, you need to put it in before this point.
<?php endwhile; ?>
This section, immediately after the end of The Loop, displays navigation controls to move forward and backward by each web page. More information is available in function reference for posts_nav_link().
<div class="navigation">
<div class="alignleft"><?php previous_posts_link('« Previous Entries') ?></div>
<div class="alignright"><?php next_posts_link('Next Entries »','') ?></div>
</div>
If the blog is set to display 10 posts per page, and the conditions used by The Loop collect 25 posts, there will be three pages to navigate: two pages of 10 posts each, and one page of 5 posts. The navigation links will allow the visitor to move forward and backward through the collection of posts.
The navigation controls are included outside The Loop, but inside the if condition, so that they only show up if there are any posts. The navigation functions themselves also check whether or not there is anything to which they will link, based on the current Loop, and only display links if there's something to link.
<?php else : ?>
<h2 class="center">Not Found</h2>
<p class="center">
<?php _e("Sorry, but you are looking for something that isn't here."); ?></p>
The else : clause determines what to do if have_posts() (from way up at the top) is false. That is to say, the stuff after the else will only be executed/displayed if The Loop had zero posts. No posts show up if, for example, the visitor requested a specific day for which no posts were made or a search was performed that produced no results.
<?php endif; ?>
This ends the conditional test of "if there are posts do this, else if there are no posts, do that". Once the conditional test is finished, the default index.php template next includes the sidebar, and finally the footer.
WordPress can use different template files for displaying your blog in different ways. In the default WordPress theme, there are template files for the index view, category view, and archive view, as well as a template for viewing individual posts. Each of these uses The Loop, but does so with slightly different formatting, as well as different uses of the template tags.
For any view which does not have a separate template file, WordPress will use index.php by default. If a visitor requests a single post, WordPress will first look for a file named single.php. If that file exists, it will be used to present the post to the visitor. If that file does not exist, WordPress will use index.php to present the post to the visitor. This is called the Template Hierarchy.
If you are making your own Theme, it's often helpful to look at the template files from the default Theme as a point of reference. It's also helpful to use your theme's index.php as a template for your other template files. Doing so may give you a known and working page from which to begin making changes as you create more template files.
An archive is a collection of historical posts. In the default usage, the posts displayed on your main index are recent chronological postings. When a visitor clicks on one of your archive links, or if they manually request a specific date (http://www.example.com/blog/index.php?m=200504 or http://www.example.com/blog/2005/04 to select all posts from April, 2005), WordPress will display an archive view. By default, the archive will use index.php, and thus look the same as your front page, just displaying the posts from April 2005.
When WordPress prepares an archive view for a visitor, it specifically looks for a file named archive.php in your current theme's directory. If you'd like to visually disambiguate archives from your front page, simply copy index.php to archive.php, and edit archive.php as necessary!
For example, if you want to show only post titles, and no post content, for your list of archives, you could use something like this:
<?php get_header(); ?>
<div id="content" class="narrowcolumn">
<?php if (have_posts()) : ?>
<?php while (have_posts()) : the_post(); ?>
<div class="post">
<h2 id="post-<?php the_ID(); ?>">
<a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>"><?php the_title(); ?></a></h2>
<small><?php the_time('F jS, Y') ?> <!-- by <?php the_author() ?> --></small>
</div>
<?php endwhile; ?>
<div class="navigation">
<div class="alignleft">
<?php posts_nav_link('','','« Previous Entries') ?>
</div>
<div class="alignright">
<?php posts_nav_link('','Next Entries »','') ?>
</div>
</div>
<?php else : ?>
<h2 class="center">Not Found</h2>
<p class="center"><?php _e("Sorry, but you are looking for something that isn't here."); ?></p>
<?php endif; ?>
</div>
<?php get_sidebar(); ?>
<?php get_footer(); ?>
Like the archive views, WordPress looks for a separate template file for category views. If a visitor clicks on a link for a category in your blog, they will be taken to the category view. WordPress will prepare The Loop with posts from that category only, limiting the number of posts per the blog's default settings.
To make your category view different from your index view, copy index.php and rename it category.php. For a category view, it's probably not necessary to list the categories to which a post is assigned, so let's remove that portion. Instead, let's announce the category at the top of the page:
<?php get_header(); ?>
<div id="content" class="narrowcolumn">
<p>
<strong>
<?php single_cat_title('Currently browsing '); ?>
</strong><br />
<?php echo category_description(); ?>
</p>
<?php if (have_posts()) : ?>
<?php while (have_posts()) : the_post(); ?>
<div class="post">
<h2 id="post-<?php the_ID(); ?>">
<a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>">
<?php the_title(); ?></a></h2>
<small>
<?php the_time('F jS, Y') ?>
<!-- by <?php the_author() ?> -->
</small>
</div>
<?php endwhile; ?>
<div class="navigation">
<div class="alignleft">
<?php posts_nav_link('','','« Previous Entries') ?>
</div>
<div class="alignright">
<?php posts_nav_link('','Next Entries »','') ?>
</div>
</div>
<?php else : ?>
<h2 class="center">Not Found</h2>
<p class="center"><?php _e("Sorry, but you are looking for something that isn't here."); ?></p>
<?php endif; ?>
</div>
<?php get_sidebar(); ?>
<?php get_footer(); ?>
As explained in the Template Hierarchy, it is possible to create separate template files for each category. Simply name the file category-X.php, where X is the numerical ID of the category. Consider carefully whether you need a whole new template for a specific category.
Let's look at two categories, "Plants" and "Flowers", with category IDs 3 and 4, respectively. Next to each post title in the output you want to have picture of either a plant, or a flower, depending on which category is being displayed. You could:
<?php if (is_category('3') ):
// we're in the Plants category, so show a plant ?>
<img src='/images/plant.png' alt='a plant' />
<?php } elseif (is_category('4') ):
// we're in the Flowers category, so show a flower ?>
<img src='/images/flower.png' alt='a pretty flower' />
<?php endif; // end the if, no images for other other categories ?>
If you added another category, "Cars", which you wanted to display in a significantly different way, then a separate category-X.php would be more appropriate.
Many users want to create separate CSS files for a specific category. This, too, can be easily accomplished. It is important to remember that stylesheets are defined and loaded in the <head> section of the HTML document. WordPress uses the header.php file for this. In the default header.php, find this line:
<link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>" type="text/css" media="screen" />
And change it to something like this:
<?php if ( is_category('5') ) { // Load special CSS for "Cars" category ?>
<link rel="stylesheet" href="<?php bloginfo('template_url'); ?>/category-5.css" type="text/css" media="screen" />;
<?php } else { ?>
<link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>" type="text/css" media="screen" />
<?php } ?>
Note: The Cars template uses the category-5.css file to override the default layout. In this example the CSS file is named after the category template file to which it will be applied, rather than the actual name of the category. Thus, you know that category-5.css goes with category-5.php.
When viewing any single post (or permalink), WordPress will use single.php, if present.
This portion, from the WordPress default single.php, provides the post meta data information about the current post:
<p class="postmetadata alt">
<small>
This entry was posted on <?php the_time('l, F jS, Y') ?> at <?php the_time() ?>
and is filed under <?php the_category(', ') ?>.
You can follow any responses to this entry through
the <?php comments_rss_link('RSS 2.0'); ?> feed.
<?php
if ( comments_open() && pings_open() ) {
// Both Comments and Pings are open
?>
You can <a href="#respond">leave a response</a>, or
<a href="<?php trackback_url(display); ?>">trackback</a>
from your own site.
<?php
} elseif ( !comments_open() && pings_open() ) {
// Only Pings are Open
?>
Responses are currently closed, but you can
<a href="<?php trackback_url(display); ?> ">trackback</a>
from your own site.
<?php
} elseif ( comments_open() && !pings_open() ) {
// Comments are open, Pings are not
?>
You can skip to the end and leave a response. Pinging is currently not allowed.
<?php
} else {
// Neither Comments, nor Pings are open
?>
Both comments and pings are currently closed.
<?php
}
edit_post_link('Edit this entry.','',''); ?>
</small>
</p>
This sort of information -- whether comments are open or closed -- is largely inappropriate on an index, archive, or category view; which is why it's only included in the single.php template file.
Now that you have a good introduction to the basic uses for the WordPress Loop, let's introduce you to some more Loop effects and tricks.
How can you display something special only on the front page of your blog? That's right, only on the front page or home page, and have it not be seen anywhere else on your site. Easy! We call this the static front page. The front or first page of your site isn't really static. It's just using the Loop to make it look that way.
To make this Loop trick work, use the is_home() conditional template tag function.
In your index.php, use an if () test to conditionally output additional content:
<?php get_header(); ?>
<?php if (is_home()) {
// we're on the home page, so let's show a picture of our new kitten!
echo "<img src='/images/new_kitty.jpg' alt='Our new cat, Rufus!' />";
// and now back to our regularly scheduled home page
} ?>
The function is_home() will only produce a true value if the visitor is not requesting a specific post, page, category, or date, so it only shows up on the "home" page.
For more information, see Creating a Static Front Page.
The easiest way to display excerpts, instead of the full content of posts, is to replace all instances of the_content() with the_excerpt(). If you have not created explicit excerpts for your posts, this function will automatically display the first 55 words of the post.
<div class="entry"> <?php the_excerpt(); ?> </div>
In some circumstances, for example on archive pages, you may want to show the full post if there is only one post or excerpts if there are multiple posts. You can customize the loop to do this.
<?php if (have_posts()) : ?>
<?php if (($wp_query->post_count) > 1) : ?>
<?php while (have_posts()) : the_post(); ?>
<!-- Do your post header stuff here for excerpts-->
<?php the_excerpt() ?>
<!-- Do your post footer stuff here for excerpts-->
<?php endwhile; ?>
<?php else : ?>
<?php while (have_posts()) : the_post(); ?>
<!-- Do your post header stuff here for single post-->
<?php the_content() ?>
<!-- Do your post footer stuff here for single post-->
<?php endwhile; ?>
<?php endif; ?>
<?php else : ?>
<!-- Stuff to do if there are no posts-->
<?php endif; ?>
WordPress offers the get_header(), get_sidebar(), and get_footer() Include Tags for use in your template files. These functions make it easy to define a standard header/sidebar/footer which is easily editable. Any changes made to these files will immediately be made visible to viewers, without any work on your part.
But sometimes you might not want a sidebar. If you don't want a sidebar, simply exclude the call to the get_sidebar() function from your template. For example, the single.php template in the WordPress default theme does not include a sidebar.
To create your own different sidebar, you have two choices:
<?php include(TEMPLATEPATH . '/sideleft.php'); ?>
In WordPress Version 2.5 and above you can also call a sidebar like this:
<?php get_sidebar('right'); ?>
This causes the template TEMPLATEPATH . 'sidebar-right.php' to be included.
Using the WordPress default Template Hierarchy, if you want to use the same elements on multiple or different templates, it's probably best to put them in separate template files and use the PHP include() function. If the element you're adding is specifically for one template file, it's probably best to include it directly in that template file.
We've just scratched the surface of what can be done with the Loop. As a reminder, the following are resources that will help you customize your own WordPress Loop.