First Impressions of Custom Post Type

February 11th, 2010 by Frank • WordPress News • 13 Comments

One of the new very interesting things in WordPress 3.0 are individual post-types you can implement with little effort. Back then, you had to expand the database and write your own interface for it, now you just have to add a few lines of code – of course this is just the current state, which can be change until the final release.

After Justin had been playing with these types, we check out the possibilities of types for “Movies”.

Simple Solution

function post_type_movies() {
	register_post_type( 'movies',
                array( 'label' => __('Movies'), 'public' => true, 'show_ui' => true ) );
	register_taxonomy_for_object_type('post_tag', 'movies');
}
add_action('init', 'post_type_movies');

More parameters for meta-boxes

Of course there are a number of parameters for this function and so the behavior and appearance of the corresponding edit page can be controlled quite easily, a small sample with additional meta boxes:

function post_type_movies() {
	register_post_type(
                     'movies',
                     array('label' => __('Movies'),
                             'public' => true,
                             'show_ui' => true,
                             'supports' => array(
                                        'post-thumbnails',
                                        'excerpts',
                                        'trackbacks',
                                        'custom-fields',
                                        'comments',
                                        'revisions')
                                )
                      );
	register_taxonomy_for_object_type('post_tag', 'movies');
}
add_action('init', 'post_type_movies');

The default arguments

// Args prefixed with an underscore are reserved for internal use.
$defaults = array(
    'label' => false,
    'publicly_queryable' => null,
    'exclude_from_search' => null,
    '_builtin' => false,
    '_edit_link' => 'post.php?post=%d',
    'capability_type' => 'post',
    'hierarchical' => false,
    'public' => false,
    'rewrite' => true,
    'query_var' => true,
    'supports' => array(),
    'register_meta_box_cb' => null,
    'taxonomies' => array(),
    'show_ui' => null
);

• label – A descriptive name for the post type marked for translation. Defaults to $post_type
• public – Whether posts of this type should be shown in the admin UI. Defaults to false
• exclude_from_search – Whether to exclude posts with this post type from search results. Defaults to true if the type is not public, false if the type is public
• publicly_queryable – Whether post_type queries can be performed from the front page. Defaults to whatever public is set as
• show_ui – Whether to generate a default UI for managing this post type. Defaults to true if the type is public, false if the type is not public
• inherit_type – The post type from which to inherit the edit link and capability type. Defaults to none
• capability_type – The post type to use for checking read, edit, and delete capabilities. Defaults to “post”
• edit_cap – The capability that controls editing a particular object of this post type. Defaults to “edit_$capability_type” (edit_post)
• edit_type_cap – The capability that controls editing objects of this post type as a class. Defaults to “edit_ . $capability_type . s” (edit_posts)
• edit_others_cap – The capability that controls editing objects of this post type that are owned by other users. Defaults to “edit_others_ . $capability_type . s” (edit_others_posts)
• edit_others_cap – The capability that controls publishing objects of this post type. Defaults to “publish_ . $capability_type . s” (publish_posts)
• read_cap – The capability that controls reading a particular object of this post type. Defaults to “read_$capability_type” (read_post)
• delete_cap – The capability that controls deleting a particular object of this post type. Defaults to “delete_$capability_type” (delete_post)
• hierarchical – Whether the post type is hierarchical. Defaults to false
• supports – An alias for calling add_post_type_support() directly. See add_post_type_support() for Documentation. Defaults to none
• register_meta_box_cb – Provide a callback function that will be called when setting up the meta boxes for the edit form. Do remove_meta_box() and add_meta_box() calls in the callback
• taxonomies – An array of taxonomy identifiers that will be registered for the post type. Default is no taxonomies. Taxonomies can be registered later with register_taxonomy() or register_taxonomy_for_object_type()

Including Custom Taxonomies

In the following example we include in our Post-Type a Taxonomy with two possibilities; own Tags and categories for Post-TypeMovies, the classical tag, without hierarchy and one as category, tag with hierarchies.

function post_type_movies() {
	register_post_type(
                'movies',
                array(
                        'label' => __('Movies'),
                        'public' => true,
                        'show_ui' => true,
                        'supports' => array(
                                     'post-thumbnails',
                                     'excerpts',
                                     'trackbacks',
                                     'custom-fields',
                                     'comments',
                                     'revisions')
                )
        );

	register_taxonomy( 'actor', 'movies', array( 'hierarchical' => true, 'label' => __('Actor') ) );

        register_taxonomy( 'production', 'movies',
		array(
                         'hierarchical' => false,
			 'label' => __('Production'),
			 'query_var' => 'production',
			 'rewrite' => array('slug' => 'production' )
		)
	);
}
add_action('init', 'post_type_movies');

Definitely a very interesting and useful feature which provides many possibilities to play around with.

Gentlemen, start your engines! WordPress 2.9 is just around the corner. Unlike WordPress 2.8, which Mark Jaquith describes as the Snow Leopard of WordPress since most of the basis of the WordPress 2.8 upgrade was complete rewrites and optimization of the infrastructure that ran WordPress instead of providing lots of new features in the same way Apple’s new OS X release is a focus on improved performance instead of features, WordPress 2.9 brings major new “bling” to the table. As a reminder of WordPress 2.8, you can see the writeup that Jonathan Dingman brought us last time around.

By and large, this release is a plugin developers release with lots of new APIs and abstraction. However, there are significant additions for theme designers and users as well. As a result, unlike previous iterations of this article (I do one for every major WordPress release), I’m going to break this down into sections for each kind of feature.

Themes: the_post_thumbnail()

Theme developers have a new piece of functionality that have become extremely popular in themes these days. As blogs have evolved from journal form into entities that can be very magazine-like, the use of thumbnail images has also grown. Typically, this layout is achieved through the use of custom fields that must be manually created and populated. No more!

As of WordPress 2.9, if you use the built in image uploader, then WordPress handle this for you. Theme designers that wish to support this feature can add the template tag the_post_image() to their themes to achieve proper placement as required by the theme layout. The template tag can optionally take a “size”, which is one of the WordPress default sizes: thumbnail, medium, large, etc. If none is provided, it defaults to your preset thumbnail size.

Example:

1 2 3 4 5 6 7 8 9

while( have_posts() ) : the_post(); ?> the_title() ?> the_post_thumbnail() ?> the_content() ?> endif; ?>

Conveniently, if a theme is enabled for post thumbnails, the only “feature” currently offering this support in WordPress, then a new “meta box” will be displayed on the Write screen allowing you to assign a post image.

Themes: Register Support for WordPress Features

Editorial Note: Since this article was published, the code has changed to refer to post-thumbnails, not post-images. As a result, function names have also change. The code and examples included before reflect this change. Sorry for the confusion and sorry specifically to theme devs who have implemented the_post_image() feature already. Just change it to the_post_thumbnail()

This may seem to be an obscure feature, and typically, it’s pretty simple to figure out what I’m talking about just by looking at the header. In this case, it’s a bit more obscure because it suggests a feature that is introduced in WordPress 2.9 and then only for a very niche purpose. I can see this being built out over time, and plugin authors can supply their own use cases.

The concept is simple. If a feature exists — in the core, the only use case is for the thumbnails I described earlier and it is called ‘post-thumbnails’ — then a theme can declare support for the feature using the add_theme_support() function in the theme functions.php. It can only be declared in this file and it requires a feature be assigned a name. As I mentioned, with WordPress 2.9, there is only one feature that is named and that is post-image. Plugin authors can provide their own new functionality using the require_if_theme_supports() function.

1	require_if_theme_supports(‘my-custom-feature’,'/path/to/custom-lfeature-library.php’);

Themes would then enable support for the feature by including the following in their functions.php file.

1 2	if ( function_exists( ‘add_theme_support’ ) ) add_theme_support( ‘my-custom-feature’ );

We’ve used the function_exists() check on the add_theme_support() function to ensure backwards compatibility with WordPress installations prior to WordPress 2.9. Similarly (and possibly confusingly in this context), before you would have to check for the existence of a plugin by using a function_exists() or class_exists() piece of logic and loading it if the class or function did exist, but now there are on/off switches to get it done.

Users: The Trash Can

On Windows, they call it the Recycle Bin. On Macs, it’s the Trash. In both cases, the feature exists to help people recover from accidental deletions. We have all had those moments where we nuked something we had no intention of nuking. With WordPress, accidental deletions have been permanent. In WordPress 2.9, everything is recoverable now with a new Trash feature. When you delete a post, page, category, comment, or any bit of content, it is moved to the Trash where you can decide whether to pull it back at a later date.

The Trash Can view. From here, content can be restored or deleted permanently.

Trash collection is done every 30 days by default, but it is possible to change this by editing your wp-config.php file. Add the following to your config file to change trash collection to every 7 days. Modify as needed.

1	define(‘EMPTY_TRASH_DAYS’,7);

Users: Image Editing

One of the hot new features in WordPress 2.9 is image editing. Now don’t get me wrong. This isn’t Photoshop. And it only support basic functionality at this time. However, image editing will allow bloggers to crop, scale and rotate images from right within WordPress. From the media library, you can edit images by clicking the Edit link under an image, and then clicking the Edit button on the individual image page. This brings up an interface like what is shown below.

The WordPress 2.9 Image Editing Screen

Users: oEmbed

oEmbed, as described at oEmbed.com, is a specification that allows media providers like Flickr, YouTube and others to provide data for consumer applications like WordPress about media. So by including an Embed (Use the File uploader and choose “From URL” and paste the link to the page that contains the media, not the media file itself) in a post or page, WordPress can retrieve the relevant specs on the media file and formulate a properly formatted embed accordingly.

Below is an embed of one of my Flickr photos using oEmbed.

Below, is an oEmbedded YouTube video (Original video removed so here’s the Iron Man 2 Trailer).

If you don’t want to use the GUI for this stuff, you can simply wrap the URL to the media page in embed shortcode tags like this.

1	<a href="http://www.youtube.com/watch?v=ZGp220EQUis&feature=popt00us0a">http://www.youtube.com/watch?v=ZGp220EQUis&feature=popt00us0a</a>

The list of supported oEmbed sites in WordPress are as follows:

• YouTube (via oEmbed)
• Blip.tv (via oEmbed)
• Flickr images and videos (via oEmbed)
• Hulu (via oEmbed)
• Viddler (via oEmbed)
• Qik.com (via oEmbed) — never heard of this site, but it was listed on oEmbed’s website, so…
• Revision3 (via oEmbed)
• Google Video (via an internal handler)
• PollDaddy (via an internal handler)
• DailyMotion (via an internal handler)

That said, plugin authors can add new providers if they want by using the oembed_providers filter or override altogether with the WP_oEmbed->providers property.

Plugins: Custom Post Types

One of the strengths of Drupal has been its ability to have multiple types of contents contained in objects that all look alike to PHP. WordPress has supported a variety of content types as well, but it has not been nearly as flexible making WordPress a blog platform with some additional support for pages and attachments. Technically, the only post_types that WordPress has supported have been post, page, revision and attachment. While it has technically been possible to add new post_types (like podcast, mp4, or tutorials – they could be anything, really), it has been a chore and required plugin developers to handle quite a few moving parts in order to make it all work properly.

No longer. Plugin authors now have API to register new post types, opening up the possibility for even more creativity and uses for WordPress.

get_post_type()

The get_post_type() function can only be used in the Loop. It returns the type of post a post is. Keep in mind, I’m using post loosely. All content in WordPress is kept in the posts table thereby inheriting the name “post”, but post is also a kind of content that is associated with blog content (as opposed to page which is a pseudo-static page, attachment which is information about an image or file uploaded with the media uploader, etc).

get_post_types()

The get_post_types() function will return a list of all types of post content. By default, this will be post, page, attachment and revision. Refer to the source code for optional arguments that can be used to control what kind of data is returned.

register_post_type()

As a plugin author, you can use this function to create a new post type. The first argument is the unique handle you want to assign to the post type – let’s call it podcast – and the second argument is an array that contains additional elements. The key one here is an exclude_from_search, which by default is set to true. You actually probably want to set this to false unless you really don’t want this additional content searchable. See below for example usage.

1 2 3 4 5

function wpb_podcast_init() { register_post_type(‘podcast’,array(‘exclude_from_search’ => false) ); } add_action(‘init’,'wpb_podcast_init’);

There is currently no user interface for post types. There is a patch in for UI that will likely be included in WordPress 3.0.

Plugins: Comment Meta

There has been a variety of meta tables in WordPress. Meta tables, like usermeta or postmeta, are database tables that contain information about the type of data that is stored in WordPress. It allows plugins and WordPress to assign metadata, such as user roles and capabilities, to pieces of data thus extending that data. Now, there is a comment meta table as well.

Though it is unclear how plugin authors will seek to use this table, the fact that it is available is a major deal as it essentially provides meta tables for every piece of content in WordPress now.

Plugins: Metadata API

With the addition of a comments meta table, it has become effectively redundant to duplicate functions throughout WordPress. You have a get_post_meta() function that does the same thing as a get_usermeta() function except they query data from different tables that also look identical except for the data stored in them.

In WordPress 2.9, there is an entirely new Metadata API that can be used to retrieve data from any of these meta tables.

The add_metadata() function takes a meta type (‘comment’, ‘post’, ‘user’, etc), the ID of the content type, the key and value of the metadata and whether the information should be unique or not (true or false).

1	add_metadata(‘comment’, 12345, ‘twitter_id’, ‘someyoungpunk’);

You can also use update_metadata(), delete_metadata(), get_metadata() and update_meta_cache() for further wrangling. Refer to wp-includes/meta.php for full documentation.

Themes/Plugins: Theme System Modification

A lot of messiness has been eliminated in WordPress 2.9 theming. For one, new template opportunities exist. Now, instead of looking for a template file called category-x.php, tag-x.php or page-x.php, where x is the ID of one of those types of content types, it will look for these templates second. The first template that is now looked for is based on the slug. So if you have a category, tag or page called foo, the first template to be sought after would be category-foo.php, tag-foo.php, or page-foo.php. If none of these templates exist, then the ID-based template file is looked for.

Additionally, plugin developers can register new directories for themes to be located with the register_theme_directory() function.

System: Database Repair Script

The database occasionally needs a good spring cleaning. Other times, the database needs a repair. WordPress ships with a new script that will do just this. It is housed at /wp-admin/maint/repair.php but in order to use it, you need to create a new (or modify if it already exists for some reason) constant in wp-config.php.

1	define(‘WP_ALLOW_REPAIR’,true);

System: Minimum Requirements

PHP 5 is not required yet. That’s coming in WordPress 3.0 will be increasingly implemented over time. But MySQL requirements have been boosted from MySQL 4.0 to MySQL 4.1.2.

Bonus coverage

Other interesting things in WordPress 2.9.

• JSON compatibility, before only beneficial to PHP 5.2, has been backported for use in WordPress
• New ‘Undo’ button when using the Visual Text Editor
• A new sanitization API (with functions like esc_html())
• The emoticon system can be altered using the smilies_src hook.
• Bulk Upgrading of plugins
• Filesystem optimizations pertaining to FTP/SSH etc.
• rel=”canonical” for single posts and pages aiding in SEO
• Minify Admin CSS making for quicker (and smaller) page loads
• Bunny Tags and Jeromes Keywords Importers removed

Popularity: 100% [?]

11 Non-Traditional Uses of WordPress

By Steven Snell | March 1st, 2009 in design

WordPress is probably the most popular blogging platform and it can also be used as a CMS to power other types of websites, such as a portfolio site. However, with some creativity and a growing number of available resources, WordPress’s limits seem to be expanding constantly.

In this article we’ll take a look at a combination of tutorials, plugins and themes that can help you to use WordPress in non-traditional ways. Hopefully you’ll find something that you can use, or at least something that will be a valuable learning resource for extending your knowledge and skills of working with WordPress.

1. Membership Directory

Last year Chris Cagle wrote a tutorial, How to Use WordPress as Membership Directory, at WPDesigner. Chris uses WordPress to power his directory, Pittsburgh Designers. The tutorial uses a few plugins for users and role management, and the end result is a moderated directory that allows members to enter information about themselves.

Update: Chris has posted a follow up to this tutorial since the release of WP 2.7 – The New and Improved Way to Turn WordPress 2.7 into a Membership Community.

2. Business Directory

The Business Directory Plugin for WordPress accomplishes a similar end result as the tutorial above. The plugin will allow you to create a directory on your website or blog where users can submit information about themselves or their business.

3. Ffffound Clone

Assualt Blog has an interesting tutorial where Tim shows how he built a Ffffound clone on WordPress. Ffffound is a great site for inspiration, and a sort of image bookmarking service for those who have access. Tim shows that WordPress can be used to build your own personal version, and he even has a working finished product, VNovember, that you can check out. The tutorial shows you how to set up the theme that Tim developed, which plugins to install, and how to make it all work.

4. Job Board

Niche job boards are now pretty common, especially in the design and development industry. The design job board here on DesignM.ag is using a great premium WordPress plugin called WPJobAds to power the job board. You could, of course, build this type of functionality into WordPress manually if you had the time and desire, but WPJobAds makes the process easier.

RecruitPress is a fee job board option. It is not a plugin, but rather a group of plugins and some core file modification that you install on top of WordPress.

I highly recommend that you do NOT buy the JobPress premium WordPress theme. I bought it, it didn’t work out of the box, and I got no response to my emails for support. The owners seemed to disappear as their site went down for an extended period, but it looks like it’s back now.

BlueFur also has a job board script that can be downloaded and used for your own job board. It’s more labor intensive than WPJobAds, but it is free.

5. Techmeme News Clone

Raj Dash wrote an article for Performancing that covers the process of using WordPress to build a “Techmeme River of News Clone.” This approach will not allow you to duplicate exactly what Techmeme does, but it is a cool idea that could be used in a variety of different scenarios.

In the article, Raj refers to a tutorial on Devlounge for mashing up feeds with Yahoo! Pipes. This is what Raj uses to create the river of news (a stream of headlines from a selection of blogs).

6. Email Newsletter

One of the older articles on NETTUTS is Build a ‘WordBurner’ Email Newsletter Manager Using WordPress and FeedBurner. WordPress and FeedBurner are obviously used together by thousands of bloggers, but in this tutorial you’ll learn how to create an email-only newsletter with content that does not show up on the front page of the blog.  The tutorial shows the manual process for “hiding” the newsletter category on the blog, but you could also achieve the same thing with the Advanced Category Excluder plugin if you don’t want to deal with the code.

7. Forums

While there are a number of options for hosting a forum on your site, it’s also possible to use WordPress. TheDeadOne.net offers the TDO Forum WordPress Theme. The theme will give you forum functionality, although you’ll most likely want to customize the design in some way. (Note: It only claims to be tested through WordPress 2.5).

8. Contact Manager

It’s also possible to use WordPress as your own contact manager. The WP Contact Manager Theme was developed for this purpose. It is a free theme that makes the blog a functional contact manager that can be extended further with some free plugins.

WP-CRM is another theme for turning WordPress into a contact manager. With WP-CRM you can add contacts and notes from the front end of WordPress without being in the admin dashboard.

9. Wiki

WordPress Wiki is a premium theme ($30) available at ThemeForest. This theme makes it easy to use WordPress for your own wiki. As expected, it’s not as robust as some other options, but it’s a great way to add a simple wiki to an existing site without a lot of effort or cost.

10. Review Site

WP Review Site is a premium plugin ($97) that will turn WordPress into a review site where visitors can place their own reviews and rate the listings. It also comes with a WordPress theme and some affiliate marketing tools. WP Review Site can be used as part of another site, or it can be used to set up a site dedicated to reviews.

11. E-Commerce

WP e-Commerce is a surprisingly powerful free plugin that will allow you to sell items through your WordPress-powered site or blog. While WordPress is not intended to compete with platforms that have been developed specifically for e-commerce, this plugin is ideal for bloggers and website owners who want to set up a small store without a lot of effort or expense.

Google Analytics recently added a new feature, called Alerts. At first glance, it’s an elegant way to show someone when a KPI on their site has changed significantly from what’s expected. It’s baselining, applied to all KPIs — even the ones you’re not looking at.