If you use any given tool for a long enough period of time you will find problems with it no matter how perfectly crafted it might be. WordPress is a tool like this that does a spectacular job of managing content as a barebones application but when you start modifying it to suit your own unique needs it can also impact the performance of it whether it really slows down or just seems like it has. Here are some basic tips and troubleshooting steps if it seems like your installation has started exhibiting signs of sub-par performance.
1. Plugins are often a source of grief for WordPress users as they are developed (usually) outside the framework of the application and, in the case of older plugins, may use features of WordPress that are deprecated and on their way out of use. One of the first steps that you can take to test this out is to disable all plugins via the link at the bottom of the Plugin page in the administration area and then reactivate each of them one at a time until you can isolate the one exhibiting problematic behavior. Usually this examination will yield a plugin that is badly outdated. Find the newer version of the plugin and try it out. In most cases, this will solve the problem but if the behavior persists then report the situation to the plugin developer and do a quick search of the WordPress forums to see if other users are experiencing the same problem. The forums can often give you ideas of how to work around the problem.
It can also be helpful to use the plugins that are available from the WordPress Plugins repository as newer versions of WP actually track the versions of plugins and will notify you via the Plugin screen when newer versions are available. Take advantage of this feature whenever it is possible as it will save you valuable time searching around when you experience an issue with a plugin.
2. Consider caching. If your public facing pages are loading slowly you might want to consider the use of a plugin like WP Super Cache to make pages load faster. This plugin won’t help you as a registered user but it will reduce the overall system load by serving up static pages to visitors who don’t leave comments. This will also protect your server from getting crushed should you be linked from a huge aggregation site like Digg or other sites that generated huge amounts of incoming traffic.
3. Examine your logs. Translate that title into “talk to your service provider” if you’re using a hosted site as they may grant you access to your logs or help you identify potential problems that may show up in system logs. There isn’t an easy answer using this suggestion as hosting environments vary wildly but what you’re looking for are repeated errors that happen with regularity and the sources of the error.
4. Look at your database. WordPress relies on a database to store everything so problems with the database or connections to it are another potential source of complications. Unfortunately diagnosing database problems from within WP isn’t possible at the present but most hosted environments will have some access tool that allows you to examine databases. PHPMyAdmin is the most common of these and you can use it to analyze your database tables and repair damaged tables if it is necessary.
5. Look at your situation. If you’re dealing with a lot of traffic and a tiny hosting company or some antiquated hardware of your own that seemed good enough when you started then you need to strongly consider upgrading your hosting solution. Take it as a measure of success that people want to access your site and realistically reassess what you need to continue delivering the same content without crushing your host or your machine.
Spam is a problem that plagues any resource on the Internet that allows any kind of user input. The unscrupulous denizens of the Web are constantly on the look out for more ways to include profitable URLs in accessible locations on the Net and as the awareness and popularity of blogging increases so does the allure of utilizing it for profit. In the blogging universe, this has largely meant comment spam. Comment spam is usually attached to older entries (in hope of escaping the notice of admins) and unrelated to the content of the entries to which they are attached. It’s annoying and a problem that will likely never end. Luckily there are more than a few ways to fend off the would-be exploiters in ways that will save you time and energy better spent adding content to your blog rather than weeding out the rotten apples. Here are five WordPress plugins that can help in this process:
1. Akismet. Akismet would be popular even if it wasn’t incredibly effective because Matt Mullenweg the head honcho of WP development is its creator. Luckily, it is as good as its reputation at dealing with comment spam. It works by comparing comments to a huge database of information about spammers already recorded and taking action against those comments when appropriate. Usually suspect comments are quarantined for a period of 15 days. What makes this tool especially valuable is that it is adaptive to prevent the poisoning of the database with false positives. If Akismet marks a legitimate comment as spam then not only can you transfer it out of the spam queue but it is also reported back to the database as a false positive. This one is included with every download of WordPress so all you really need to do to take advantage of it is to head over to WordPress.com to sign up for a user account, grab your API key, and activate the plugin in the WP dashboard.
2. Peter’s Custom Anti-Spam. This is a Captcha solution to the comment spam problem. Users are prompted to enter a word before they can successfully submit a comment. This is effective in combatting the use of automatic spam bots that try to leave as many comments as possible. This also allows you to granularly control how the plugin is doing its job by creating your own list of source words and selecting whether or not registered users will have to complete the Captcha in order to leave comments.
3. Bad Behavior. Bad Behavior takes a more radical approach to dealing with the problem of comment spam. It filters all requests to your site through a filter that looks at how people are accessing your website in addition to the comment they are trying to add. The advantage here is that BB can spare you the bandwidth costs associated with spam robots that tend to make numerous attempts simultaneously. This one is a little trickier to set up as it requires a little digging around to make sure everything is properly configured but there is no dearth of documentation to help you get Bad Behavior up and running.
5. DNS Anti Spam. DNS Anti Spam compares the IP address of the commenter against a huge blacklist of known spammers and checks to make sure that there are no links in comments that match that blacklist.
This list is a short list of recommendations so it is by no means definitive. One of the most frustrating aspects of dealing with comment spam is that the battlefield is constantly changing as spammers adapt to try to work around the tools we use to minimize their harm. Many of the tools referenced above use a centralized database to track results so if given an option always enable your tools to report back when you find false positives or negatives. It’s a very simple and low impact way of giving something back to the community.
WordPress is very well used and well liked within the larger blogging community whether it for use with a very personal or specialized blog or something larger that requires static pages and a number of additional features that reach outside the normal parameters of blog functionality.
One of the reasons that so many use WordPress is that it is extremely configurable through plugins, hacking the actual WordPress code, and the functionality that comes baked in to WordPress from its initial install. Though WP is completely capable of fulfilling the needs of the average blogger (and then some), it is optionally extensible into a fully fledged system of document creation and organization.
WordPress, as either a blogging platform or Frankenstein-ed into whichever type of management solution the user would like, focuses on usability and capable simplicity. The administration interface follows the general design of the rest of the application in terms of presenting a basic interface but expanding to meet user needs when it is necessary. There are few configuration options not addressed in the panel and once accustomed to the tabbed interface — it doesn’t actually use tabs but the flow of it is identical — it is a quick way to get to the particular area of the application that you need.
Another aspect to keep in mind when considering WordPress is that is it licensed under GPL and cannot be boxed away into a commercial product that requires its users to pay for each new version. If you’re considering the creation of a derivative product that uses WordPress as a part of it you will want to read up on the GPL and how it might effect your distribution of WP code. For most users, the GPL serves as protection against the closure of access down the road. One of the reasons that so many people initially adopted WordPress was at least in part due to a licensing change in the then dominant blogging software Movable Type that stunned many people who assumed that the free use they were accustomed to had suddenly disappeared. WordPress is licensed as an open source application so that sort of sudden shift in a developer’s goals will not not constrain its use.
A side effect of the open source nature of WordPress is the huge number of people actively at work improving the software and adding additional features. This essentially means that no single developer has complete and utter control over the project; if one person becomes burned out or lacks the necessary time to contribute fully to the project then another will take up responsibility or help distribute the work between other active developers. What this means for users is that someone will always be working on getting new versions of WordPress out the the door and working on fixing the problems users report.
The WordPress website also contains an enormous amount of documentation that is available to anyone in the form of the WordPress Codex. By searching around in the Codex you will find information on how to customize any part of the application or how to solve potential problems. The WordPress Forum is another valuable tool for troubleshooting and general questions. The continually increasing user base makes both areas of their website very active and friendly. You can also find out about new plugins available for WP through the Extend section of the site and, if you’re using the 2.3 release, get updates directly through the administration interface when there are new versions of the plugins that you already use.
So, this has been a general overview of the reasons that you will want to consider WordPress as the tool for your next website whether a personal blog or as a public relations outlet for a multinational corporation. No software is a panacea and WP won’t answer every question straight out of the box. There is the overhead of adjusting things, adding plugins, and so on but it is more helpful to think of these minor bumps in the road as an investment in a tool that is adaptable to almost any use and is continually evolving to meet the needs and wants of its users.
Small Potato made a post about 404 pages for WordPress. His solution isn’t so bad, but if you want the real deal check out Dax’s F*ck 404′s for WordPress. This great little code snippet will redirect any link juice (PageRank or PR) towards your main hog (index page), at the same time as redirecting your visitors there. This means that if you delete, rename or move a popular post then the links you had pointing at that post will be redirected to point at your index page.
Whilst you’re there you might be interested in some of his (mainly SEO) WordPress plugins including the most excellent Subster Rejuvenation.
I can’t believe I am actually encouraging normal people to visit Dax’s site.
Are you still running WordPress 2.0.x or an older version? You may find that newly released themes do not work with your install. This has been something of a headache for me, especially as I have released several WP themes over the last week or so and the popular theme viewer at themes.wordpress.net still appears to be running on an old version of WordPress. The themes I was uploading there were giving an error message as early as line 2 of the header! Anyway, heres some handy tips for anyone with a similar situation.
You might not need to perform all these changes; not all themes are equal
- replace wp_list_bookmarks() with get_links_list()
- replace <?php wp_list_categories(‘show_count=1&title_li=0′); ?> with <?php wp_list_cats(‘sort_column=name&optioncount=1&hierarchical=0′); ?>
- delete <?php language_attributes(); ?>
- delete <?php the_search_query(); ?>
- replace wp_list_bookmarks() with get_links_list()