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.
Implementing a solid set of navigational links for your WordPress site is one of the best ways to encourage visitors to stick around awhile and check out additional content. For example, after you're done reading this post, you'll find a set of navigation links for the previous and next posts in the blog. So you could, if you wanted to, read through every post, one after another in sequential order.
As discussed in our definitive guide to WordPress post navigation, there are essentially three different types of navigational tags for WordPress:
BloggingPro.com’s Franky Branckaute provides an excellent guide showing how to use the WPML plugin to easily publish your blog in multiple different languages. Seems like a great alternative to free translation services like Google Translate or Babelfish, and you can even publish each translation to its own separate (sub)domain. This complete step-by-step guide shows you how.
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.
Alex Denning of WPShout.com asks 21 WordPress theme designers, developers and bloggers why they choose WordPress for their projects. This is the first of four questions that will posted over the next couple of days. Some very interesting responses so far, and a nice presentational style to boot!
Editor's note: 404 link removed.
As a dynamic blogging system, WordPress consists of PHP files (the WP core) that interact with a MySQL database to generate the web pages for your website. When everything is working properly, this dynamic interaction keeps WordPress humming along like a champ, but when your database crashes, WordPress can’t operate and will deliver the following message to your visitors:
This post was so huge I actually had to edit and post it using phpMyAdmin directly to the database -- WordPress apparently can’t handle ‘em that big! Seriously though, it’s a great post with over 75 awesome tips, tricks, and techniques for improving your WordPress site. Just some of the leftovers from the book that were too juicy to throw away ;)
Importing and displaying feeds in your WordPress themes is a great way to share additional content with your readers. Some good examples include:
Jean-Baptiste Jung, mastermind behind the popular sites Cats Who Code, WP Recipes, and the newer Cats Who Blog, reviews our new book, Digging into WordPress!
By default, WordPress generates an RSS feed for the comments on every published post. Many sites take advantage of this by displaying a feed link next to the comments area. This enables visitors to subscribe to the comment thread and stay current with conversation. It's convenient, simple, and super useful. For example, a typical feed menu for many blogs includes the following items:
One of the most powerful comment-editing solutions for WordPress just got a major upgrade. Ajax Edit Comments enables your visitors to “self-edit” their own comments, greatly improving the usability and “coolness” factor for your site. And with the latest upgrade, AEC gets even better, with a revamped popup box, easy “undo” options, comment-blacklist feature, new icon themes, increased security and tons more.
One of the best ways to ensure strong security for your WordPress-powered site is to secure its foundations during the installation process. Of course these techniques can be implemented at any point during the life of your site, but stetting them before the game starts prevents headaches and saves time. We’ll start with the WordPress database..
I think one of the biggest WordPress myths is that you need a bunch of plugins to control comment spam. Pretty much all of the posts out there on preventing WordPress comment spam are telling you to install some list of “must-have” anti-spam plugins. Some authors insist that you need only a few “choice” plugins, while others advise you to load up on everything you can get your hands on. Such advice is all well-intentioned, I’m sure, but it’s all based on the assumption that plugins are actually necessary to control comment spam. They’re not. WordPress is well-equipped to handle the job all by itself. Plugins may provide additional anti-spam functionality, but they are by no means essential to running a spam-free site.