From time to time, as my schedule permits, I plan to use this space to highlight interesting things I’ve learned about WordPress and BuddyPress since I’ve begun a full-time position developing sites on the platform.
In the few months that I’ve been in this new position, I’ve encountered many a unique situation arising from a client request. Most of these situations require some creative solutions that leverage the under-the-hood features that make WordPress (and BuddyPress) such a flexible content management system. Rather than keep these insights to myself, I will share them here for the benefit of the community.
My hope also is that some of the things I’ve learned can be turned into plugins that further expand and extend the power of WordPress and BuddyPress.
Today’s release of WordPress 3.0 brings some exciting enhancements and new features that strengthen the software’s position in the realm of content management systems. For developers such as us, two sets of features in particular should prove invaluable in implementing WordPress-based solutions for our clients.
First, version 3 expands WordPress beyond the traditional blogging constructs of posts and pages by allowing users to specify custom post types. These custom types can function either like posts, organized linearly, or like pages, having a hierarchical structure. This feature builds on the custom taxonomies introduced in WordPress 2.9, which let users expand the organizational options for content beyond just categories and tags. Now, combining custom post types with custom taxonomies, users have complete control over how content is organized and displayed.
Custom post types don’t just let users segregate press releases from product pages, for example, but also simplify the addition of fields specific to each post type. A product post type could include pricing and availability, whereas a press release could hold media contact information. Following this example, separate taxonomies can be assigned to each, reaffirming a clear organization of content.
Since switching this site to the Intense Debate (ID) commenting system, one function I missed was the ability to integrate reCAPTCHA1 into my comment forms. While I understand some are not fans of the system that adds nearly inscrutable text to a form that then must be typed in to the accompanying box to continue, the mechanism does significantly reduce the volume of comment spam.
reCAPTCHA is one form of a challenge system, known as CAPTCHA or Completely Automated Public Turing test to tell Computers and Humans Apart, developed at Carnegie Mellon University. More information is available on Wikipedia. ↩
To better showcase my web development work, I’ve relocated the pages related to my WordPress plugins to http://www.ethitter.com/plugins/. Any future announcements concerning plugin updates and new offerings will be hosted at ethitter.com.
As part of the move, my plugin development feed is now http://feeds.ldmh.us/ETHPluginDev. FeedBurner does not automatically redirect renamed feeds, so please update your reader accordingly. Anyone subscribed by email, however, should continue to receive updates.
For the past few months, I’ve helped organize the inaugural WordCamp Boston, happening this weekend in Cambridge. For the uninitiated, WordCamps are community-organized events for users of the WordPress platform of all experience levels (WordPress just so happens to power this site).
Having never organized a conference before, the experience has been enlightening, to say the least. Luckily for our attendees, my fellow organizers have much more experience with these types of things, ensuring this weekend’s event will be one of the coolest, most unique WordCamps thus far.
If you can’t make it or couldn’t get a ticket, be sure to keep an eye on wordcampboston.com throughout the day Saturday for a glimpse into what the camp holds. In the weeks following the event, videos of the sessions will be available online, likely at WordPress.tv.
Then, in the process of upgrading my site to the latest version of WordPress, I identified the true reason for my missing trackbacks. As part of the upgrade, I eliminated a few redundant plugins, including WP Captcha-Free. This plugin, which claims that it won’t block pingbacks or trackbacks, did just that.
I can confidently attribute the cause of this mystery to WP Captcha-Free because trackbacks from uberVU and Topsy once again appear in the IntenseDebate moderation queue.
After a month of confusion and consternation, I can happily report that I’ve resolved the mystery of the missing trackbacks.
On Friday, I wrote about the mysterious disappearance of trackbacks from my site. At the time, I believed I’d solved the problem by adding the trackback RDF and URL codes to my theme, as neither is included in the original design.
Now, I’m noticing that trackbacks still aren’t appearing. So, the mystery continues.
Has anyone else encountered this problem with the Journalist theme, or any other theme for that matter? If so, were you able to resolve this issue, and how did you resurrect your trackbacks?
A few weeks ago, I switched my site’s design from the Carrington framework to Lucian Marin’s Journalist theme. While I liked the visual design of the Carrington framework, it includes many features I never used. These options, in part due to problems with my host, were slowing my site down considerably. In an attempt to reduce the errors my blog generated, I switched to the Journalist theme for its lightweight coding and clean, yet appealing, design.
Shortly after making the switch, I began to notice that trackbacks weren’t appearing on my posts. At first, I assumed that the ongoing problems with my host were to blame, but since these issues have been largely resolved, I began to wonder if something else was amiss. As I discovered yesterday, the Journalist theme does not include either the trackback RDF code or trackback URLs. With the addition of one line of code, however, trackbacks are once again appearing on my posts.
If you’ve noticed the same problem with your WordPress theme, adding <!-- <?php trackback_rdf(); ?> --> to your theme’s index.php, page.php, and single.php files (just before the <?php endforeach; else: ?> line) will solve the problem. I recommend adding a trackback link, using the <a rel="trackback" href="<?php trackback_url(); ?>"><?php trackback_url(); ?></a> code as well, to ensure compatibility with the widest variety of sites.