This chart is one entire page in our book, but I thought it would be good to focus on specifically. Template hierarchy has gotten a bit more advanced since the last time we covered it.
The idea is that WordPress will look for files in a theme to use to render the current page in a specific order. For example, let say you have a page for showing posts from a certain category like this. On this site, all our category pages are currently the same and use "archive.php" template. This file is pretty far down the hierarchy, and is shared with other types of views, for example, tag and category pages.
In our recent post on pimping the wp-config.php file, we explain that using strong Security Keys is an important part of securing your WordPress installation. In this post, we want to zoom-in on Security Keys and look at what they are, how they work, and how to use them to greatly improve the security of your site.
WPCandy is back under Ryan Imel and it's been loaded with good stuff lately, including this great run-through of how to use Chris Shiflett's URL sentences idea in WordPress.
It's here! Digging Into WordPress Version 3.0 is here and it's packed with lots of awesome WordPress goodness, including an entire new chapter on WordPress 3, plus lots of updated core content, and a super-sleek new cover that I think is a huge improvement. You've got to check out the book's sweet dark/black cover, expertly crafted by Chris:
Easily, the most important file in your WordPress installation is the
wp-config.php file. It serves as your site’s base configuration file, controlling key aspects of WordPress’ functionality and enabling WordPress to do mission-critical stuff like connect to the database. Without
wp-config.php, WordPress simply won’t work. So whenever you install WordPress, one of the first things to do is pimp your
wp-config.php with some custom WP configuration tricks.
Peter Wilson walks us through making sure print stylesheets are loaded after the rest of the page is loaded, so they don't hold up page rendering.
Editor's note: 404 link removed.
Pardon my ignorance here, but Rasmus starts talking about latency and concurrent requests about 16:30. He then mentions "one line of code" installation of something that sounds like "aqua code cache" that gives WordPress a 3x performance boost in response time / number of transactions per second. Anyone knows what he's talking about there, shoot a note and I'll update this permalink with the info. He goes on to talk about much more hardcore-PHP-nerd WordPress optimization stuff.
The scoop via Joost Schuur:
Rasmus is talking about an 'opcode cache'. It essentially caches the parsed PHP scripts in memory. That means PHP doesn't have to read it from disk or even convert the humanly readable PHP script code into executable machine code (opcode). The one he's referring to is APC, which is likely going to be included in the next big release of PHP. Xcache is another popular kind. I run it on my site and got about a 3x performance increase on page request server times, so the numbers add up. The W3 Total Cache WordPress plugin has the option of using Xache or APC to keep popular pages in memory via opcode caching.
I'm all about tinkering with different ideas to display posts with WordPress. After all, it's just a bunch of data at our fingertips! WordPress makes it easy to output whatever we need. Not long ago we experimented with making a Thumbnail Based Archives. Now let's have some fun and build a Randomized Grid Archives.
Here are some sweet SQL code snippets for easy comment management. Sometimes it’s easier to modify comment status and delete unwanted comments on a sitewide basis. Using a program like phpMyAdmin makes it so easy to do stuff like remove spam, close/open comments on old posts, enable/disable pingbacks for specific time periods, and so on. Just remember to backup your database before running any queries (just to be on the safe side).
The menu system in WordPress 3.0 was hotly anticipated. But perhaps unbeknownst to many average WordPress users, actually using this feature takes some coding work. In fact, even enabling the features take a bit of code. So if you have WordPress version 3.0, but don't see the Menu item in your WP Admin Area (as shown in the Featured Image for this post), don't worry. Until you implement the required code, most likely you'll be seeing something like this:
Just a reminder that WordPress version 3.0.1 is available, so take a few moments and update your website. Staying current is one of the best ways to keep things running smooth, safe and secure. The new version addresses about 50 minor issues and helps to make WordPress 3.0 even better.
Amazingly, WordPress 3.0 was downloaded nearly 11 million times in 42 days. So HUGE congrats and thanks to the entire WordPress crew for an amazing piece of software.
We use E-Junkie ourselves on this site to sell the book. This plugin brings to two together to theoretically make that process easier.
Editor's note: 404 link removed.
We have been working diligently on updating Digging Into WordPress and finding the best print-on-demand solution. As we've covered before, the on-demand options we looked at previously left a lot to be desired. But thanks to your suggestions and ideas for book printing, there were many additional options to check out. So after sizing things up, we're pleased to announce the following: