WordPress is not PHP

WordPress is not PHPMatt Readhttp://mattread.com/?p=1932008-04-19T23:57:01-04:002013-05-02T14:50:25-04:002005-04-21T17:47:55-04:00<p>There have many concerns and question about the template system used in <a href="http://wordpress.org">WordPress</a>. Mostly the concerns are with n00bs and the complications of PHP. “I want to change this and that, but don't know PHP”. I hear this a lot. But the thing is, you don't need to know PHP to change the <a href="http://codex.wordpress.org/Templates">Templates</a> in <a href="http://wordpress.org">WordPress</a>. </p> <h2>The Template System</h2> <p>Lets' start with “<a href="http://codex.wordpress.org/The_Loop">the Loop</a>” as we call it. Probably the most confusing part of the <a href="http://codex.wordpress.org/Templates">Template</a> for a non-programmer. The Loop looks like this:</p> <pre class="highlight php"> <![CDATA[ <?php if ( have_posts() ) : while ( have_posts() ) : the_post(); ?> //Template Section 1: post content Template Tags go here <?php endwhile; else: ?>; //Template Section2: no posts found stuff here. <?php endif; ?> ]]> </pre> <p>It may look complicated, but it's actually quite simple. In <a href="#ex1">Template Section 1</a>, all the posts information will be displayed. Within that section we will put all the posts <a href="http://codex.wordpress.org/Template_Tags">Template Tags</a>, and our HTML to format them. In <a href="#ex1">Template Section 2</a>, we will display a message telling the user no posts were found, if we find none to meet their criteria. </p> <h3>Template Section 1: The Posts</h3> <p>We'll start with outputting the post tile. Simply add in the <a href="http://codex.wordpress.org/Template_Tags">Template Tag</a> <code class="html"><?php the_title() ?></code>. That will output the title of the post. </p> <p>Now let's output the date of the post. Simply add the date's <a href="http://codex.wordpress.org/Template_Tags">Template Tag</a> <code class="html"><?php the_date() ?></code>. That outputs the date of the post.</p> <p>We will also, of coarse, need the content of the actual post. Simply, again, add the <a href="http://codex.wordpress.org/Template_Tags">Template Tag</a> <code class="html"><?php the_content() ?></code>.</p> <p>Now let's put it all together with some HTML:</p> <pre class="highlight php"> <div class="post"> <h2> <?php the_title() ?> </h2> <p> <?php the_date() ?> </p> <?php the_content() ?> </div> </pre> <p>And there's our simple template. Now let's add some more.</p> <p>First let's add a link to the post, permalink as it's called, on the title. We get the actual URL, something like <code class="html">http://mysite.com/archives/2004/09/post-title/</code>, with the <a href="http://codex.wordpress.org/Template_Tags">Template Tag</a> <code class="html"><?php the_permalink() ?></code>. We will need to put that in our <code class="html"><a href=””></code> HTML tag.</p> <p>We also want to add in links to each page of our post, next page, previous page, etc.. We simply call another <a href="http://codex.wordpress.org/Template_Tags">Template Tag</a>, <code class="html"><?php link_pages('<p>','</p>') ?></code>. Now here's another confusion people have. We've added in, what programmers would call, arguments to our <a href="http://codex.wordpress.org/Template_Tags">Template Tag</a>. That is, we've added in <code class="html">'<p>', '</p>'</code> to the brackets of the <a href="http://codex.wordpress.org/Template_Tags">Template Tag</a>. In this case we are just saying, if there are pages to link, output the page links with a <code class="html"><p></code> at the start, and a <code class="html"></p></code> at the end. Hence, enclosing it all in HTML paragraph tags. Most <a href="http://codex.wordpress.org/Template_Tags">Template Tags</a> have different arguments you can pass to them, causing them to format their output differently.</p> <p>Now let's add in our new tags.</p> <pre class="highlight php"> <![CDATA[ <div class=”post”> <h2> <a href=”<?php the_permalink() ?>”> <?php the_title() ?> </a> </h2> <p> <?php the_date() ?> </p> <?php the_content() ?> <?php link_pages('<p>','</p>') ?> </div> ]]> </pre> <p>Now we have a fully functional Posts section, <a href="#ex1">Template Section 1</a>. Let's move on to <a href="#ex1">Template Section 2</a>.</p> <h3>Template Section 2: No Posts Found</h3> <p>For our <a href="#ex1">Template Section 2</a>, the no post found section, all we need to do is put in a message to tell the user nothing was found, to meet their criteria. Whether it was a search or a mis-typed URL. So let's use the following simple HTML:</p> <pre class="highlight html"> <![CDATA[ <p>Sorry, no posts could be found to match your criteria.</p> ]]> </pre> <p>Now let's put it all together.</p> <h3>Complete Template</h3> <p>Putting all we learned above together, we get a nice simple <a href="http://codex.wordpress.org/The_Loop">Loop</a> <a href="http://codex.wordpress.org/Templates">Template</a>.</p> <pre class="highlight php"> <![CDATA[ <?php if ( have_posts() ) : while ( have_posts() ) : the_post(); ?> <div class=”post”> <h2> <a href=”<?php the_permalink() ?>”> <?php the_title() ?> </a> </h2> <p> <?php the_date() ?> </p> <?php the_content() ?> <?php link_pages('<p>','</p>') ?> </div> <?php endwhile; else: ?> <p>Sorry, no posts could be found to match your criteria.</p> <?php endif; ?> ]]> </pre> <p>As you can see, we have done no PHP coding, just some simple HTML with <a href="http://wordpress.org">WordPress</a> Template Tags added in.</p> <p>Obviously this is not a complete template, as we have no header and footer containing all the <code class="html"><html><head><body></code> tags. But with some simple HTML and more <a href="http://codex.wordpress.org/Template_Tags">Template Tags</a>, and no PHP, we can easily add all that is needed for a complete HTML document. That's right, an HTML document, not a PHP script.</p> <p>As we can see <a href="http://wordpress.org">WordPress</a> is not PHP. <a href="http://wordpress.org">WordPress</a> is powered by PHP, but uses a simple template system, easily modified by even the most novice of users. None of that complicated Perl code like MT has ... Yes, believe it or not, MT is also powered by a complicated programming language. The only difference is marketing. MT has been marketed as having simple templates with no programming skills needed. However, somehow, and I don't know why, <a href="http://wordpress.org">WordPress</a> has gotten a rap of being complicated and only for the hardcore programmers out there. But as we can see, using the <a href="http://codex.wordpress.org/Template_Tags">Template Tags</a> is extremely easy and requires no knowledge of PHP at all.</p> <p>Changing the format and style of your <a href="http://codex.wordpress.org/Templates">Template</a> is as easy as using a little HTML, CSS and Template Tags. Just like other Weblog systems out there. </p> <p>However, as with any software, there is room for improvement.</p> <h2>Improving Templates</h2> <p>One of the problems with the <a href="http://wordpress.org">WordPress</a> <a href="http://codex.wordpress.org/Templates">Template System</a>, in my opinion, is the default <a href="http://codex.wordpress.org/Templates">Template</a>, or theme, itself. Specifically the sidebar, with all the <code class="html">is_*()</code> functions. We shouldn't expect a novice <a href="http://wordpress.org">WordPress</a> user to understand what these functions mean. I would suggest removing all the <code class="html">if(is_*())</code> statements in place of a simple sidebar with just the essentials. Say, Search, Pages, Archives, Categories, Links, Meta information and take out all the complicated if statements and includes.</p> <p>Another problem I see with the default <a href="http://codex.wordpress.org/Templates">Template</a> is the CSS in the header. I think all CSS should be contained in the style sheets themselves. Again remove the if statements. When a user wants to modify the CSS it seems logical to have just the simple CSS in one place, to easily modify.</p> <p>Another problem I see is with some of the <a href="http://codex.wordpress.org/Template_Tags">Template Tags</a>. Such as <code class="html"><?php bloginfo() ?></code>. Instead of having one function to display some necessary information, like blog name, description, url, etc., why not have specific tags for the highly used information. Like say, <code class="html"><?php blog_name() ?></code>, <code class="html"><?php blog_description() ?></code>, <code class="html"><?php blog_url() ?></code>, etc., to maintain consistency. For some of the less used information, charset, version, etc., the <code class="html"><?php bloginfo() ?></code> tag would be fine.</p> <p>And some of the other advanced <a href="http://codex.wordpress.org/Template_Tags">Template Tags</a> in use in the default <a href="http://codex.wordpress.org/Templates">Templates</a>, like <code class="html"><?php list_cats(0, '', 'name', 'asc', '', 1, 0, 1, 1, 1, 1, 0,'','','','','') ?></code>, should be simplified to not contain all those arguments. Maybe use <code class="html"><?php wp_list_cats() ?></code> where all those settings would be set in the admin area.</p> <p>It would also be nice to try to simplify the loop, although I can't see any way of doing that now, to use as little actual PHP, like if else statements, as possible. Also take out the else, for when no posts are found, and always use the 404 template file.</p> <p>The point I'm trying making is to take the PHP out of the <a href="http://codex.wordpress.org/Templates">Templates</a>, as much as possible, so users don't get confused and think they need PHP skills to modify the <a href="http://codex.wordpress.org/Templates">Templates</a>.</p> <p>Those are just my thoughts on the matter.</p> <p>If you need any help with your templates, or would like to learn more about the monkey, I'd be glad to help out. Just <a href="/contact/">drop me a line</a>.</p>