Here are six htacccess tricks that will help improve the security and SEO quality of your WordPress-powered site. We do this using .htaccess to establish canonical URLs for key peripheral files, such as your
sitemap.xml files. Canonicalization keeps legitimate bots on track, eliminates malicious behavior, and ensures a better user-experience for everyone. On the menu:
- Client-Side & Server-Side Validation
- Use as widget, shortcode, or template tags
- Simple CAPTCHA with tamper-proof encryption
- Smart Register Tab
ZB Toolkit also includes a couple of bonus "home-brewed utilities" to make it all sweet. Demo available at the plugin home page in the sidebar – Check it out!
Editor's note: 404 link removed.
Digging into WordPress is an entirely self-published book. It's not that way because we just arbitrarily decided that self publishing was hip and that was what we were going to do. In fact, the plan early on was the opposite. Step one, we thought, was to write the book. So we did that. Then step two became find publisher to publish it, so we asked around. We talked to five (or so) tech book publishers.
As mentioned, the v3.0 printed books are out of stock, but we're updating DigWP for WordPress 3.1 and plan on printing more books soon. In response to requests, we set up a waiting list for people who want to be notified when the new (3.1) printed books are available.
Empower your visitors to submit posts and images from anywhere on your site and from anywhere on the page. User-submitted posts may include tags, categories, post title, and author name & URL. Submitted-post status can be set to draft, publish immediately, or publish after some number of approved posts. User Submitted Posts (USP) also handles multiple image uploads, custom URL redirects, and much more. And the easy USP Settings Page makes setting up and fine-tuning a breeze.
He's posted a bunch of good, specific, detailed articles on WordPress lately on 456 Berea St. Worth checking out.
...people feel more comfortable hacking PHP did and still to this day.
...if I had a dollar every time a significant and loyal TypePad and Movable Type customer confided in me that an employee of Automattic cold called them to encourage and entice them to switch to WordPress I would have quit a rich man.
- Themes are just a folder with of handful of files. That's easy to understand and play with.
- The UI is awesome.
Regular updates keep WordPress secure and expand the feature set, ensuring the platform meets both the developer’s and their client’s needs.
The flipside of regular updates is the maintenance of WordPress installs. Once you start maintaining more than a few installs for your clients, keeping both plugins and WordPress up to date can become a bit repetitive.
I posted a little tip on CSS-Tricks the other day about how you can load only parts of other pages on a site via Ajax, and how to do that without needing additional HTML wrapping elements to keep it clean. A common criticism of this is that the Ajax request still loads the entire page, using all that bandwidth, it's just that it only places onto the page the part you specify via CSS selector.
Sometimes it's hard to have discussions like this without looking at specific use case, but I see where they are coming from. Loading content you aren't going to use is a waste of bandwidth. It does make progressive Ajax enhancements a lot easier though. And in fact, that's how our All AJAX theme works.
Looking for WordPress developers and designers? So are many people. Time is scarce these days, and we get quite a few folks asking about where to go for help with their WordPress site. Most of the WP peeps that we know are just as busy as we are, so it would be helpful to have a nice, healthy list of WordPress designers and developers all in one place that people could check out and find some good candidates. That's exactly the point of this quick DigWP post (and the following comments thread).
A common question for new WordPress designers/developers is how to handle plugin upgrades and upgrades of WordPress itself. To illustrate the meaning behind this question, consider the following real-life example. I recently logged into a client site for maintenance to find that someone had “attempted” an upgrade of WordPress, but that it had failed:
While manually upgrading a bunch of old WordPress sites, I realized that the WordPress htaccess rules for permalinks had changed. For many years and versions, the htaccess code that enables WordPress permalinks went unchanged, resulting in an almost sacred set of htaccess directives. Here are the original permalink rules as currently provided at the WordPress Codex: