Posts tagged: tips
If you have posts that include the
nofollow attribute on links, you may at some point decide to remove them. By default, WordPress doesn’t insert
nofollow attributes in post content, but there are a variety of plugins that will insert
nofollow into all links in post content.
Or perhaps you have been manually adding
nofollow tags to your post links for SEO purposes. Regardless of how they got there, it’s very easy to clean things up and remove all
nofollow attributes from post content.
The default output for WordPress’
post_class template tag includes class names for just about every type of page view imaginable:
Everyone who has been using WordPress for any length of time should be familiar with the good ol’
--> tag. When you are writing a post, inserting the
--> tag within the post text will create an excerpt out of any text/markup that precedes it. The post will then show the default “more...” link that readers may click to view the entire post. When the
more tag is used, the post’s excerpt will be displayed on all non-single views, such as category, tag, and archive views; the entire post content will only be displayed on single-post views. Let's look at a quick example..
A reader recently asked about how to develop a theme on a live site such that:
- All visitors will see the current theme
- Only the designer will see the new theme
- All site plugins will work with the new theme
- Smooth transition between old and new theme at launch
These are the main concerns, but there are a few other details that need addressed to ensure smooth theme development on a live site. Let’s take a look at how to achieve these goals and effectively develop themes behind the scenes.
Let’s say your blog is set to display ten posts per page, as specified via the WordPress Admin under Settings ▸ Reading. Once set, ten posts will appear on your home page, archive pages, search results, and so on. In other words, if it isn’t a single-view page or an actual “page” page, you’re gonna get ten posts per page. It’s a global setting.
But what if you want to display different numbers of posts for different types of page views? For example, instead of showing just ten posts on your search-results pages, you may want to show a whole bunch, like maybe fifty or something. Perhaps you would also like to limit the number of posts displayed on your category archives to only five.
Typically when you use one of WordPress functions to output a list of "stuff" from WordPress, you can pass a parameter to eliminate the "title" that WordPress likes to put in there by default. For example, with
wp_list_categories you pass along "title_li=" with nothing after the equals sign to remove the title that normally accompanies the output. With the function to output links (e.g. blogroll), you use the function wp_list_bookmarks, but unfortunately using that same parameter the same way is ineffective at removing the title.
With WordPress, there are various distinct types of page views. For example, there are category-archive views, tag-archive views, author-archive views, date-archive views, single-post views, single-page views, and so forth. And of course you know that you can target single-post views in your theme template with the conditional tag,
Inside the loop, if you use the function the_date() to display the date the post was published, you may run into trouble. Specifically, if there are two posts published on the same day, the second one will return nothing for a date.
With the dynamic nature of WordPress, creating, using, and maintaining strong passwords is critical. Passwords help keep the good guys in and the bad guys out, enabling you to run a safe, secure WordPress-powered website. In this DiW tutorial, we’re going to show you how to change your WordPress password in virtually any scenario: logged in, locked out, and everything in between.
By default, WordPress wraps HTML comments with paragraph tags:
WordPress also employs various template tags that may, in certain situations, result in empty HTML elements such as paragraphs tags:
This is something I find myself answering a lot. Excuse the snarky introduction to this post, my real goal here is to attempt to clarify what will and will not "work" with WordPress. So, to answer the question, "will this work With WordPress?!?!"...
Recently, I found myself on the front lines of WordPress’ somewhat complicated Media-Library system. The site that I was developing required a rather elaborate system of retrieving and displaying image attachments. So, using the latest version of WordPress (2.8.3 at the time), I found myself experimenting with as many template tags and custom functions as I could find. After much experimentation, I discovered the perfect solution, and along the way I collected a healthy collection of recipes for displaying image attachments and their various types of associated information.
Not everyone loves the post-revisioning feature of WordPress. In fact, some people can’t stand it. On the one hand, it’s nice to have a library of post-draft revisions to drudge through if you should ever make a mistake. On the other hand, multiple copies of every post is a great way to bloat your database with otherwise useless information.
Included in the
header.php template of most WordPress themes, there is an important hook called
wp_head. This essential hook enables WordPress functions to output content to the browser in the
<head></head> area of your web pages1.
For example, in newer versions of WordPress,
wp_head() enables WordPress to output the following three lines to your theme’s